Quickstart
This guide walks you from zero to a running pipeline with schema drift monitoring in under 5 minutes.
You'll need a source database or Kafka topic and a destination warehouse (Snowflake, BigQuery, or Redshift). No destination yet? Browse all connectors.
1. Install the CLI
Install the Queryvine CLI via pip:
Terminal
$ pip install queryvine-cli
Successfully installed queryvine-cli-1.8.4
$ qv --version
2. Authenticate
Generate an API key from your workspace settings, then authenticate the CLI:
Terminal
$ qv auth login --key qvk_live_xxxxxxxxxxxxxxxxxxxx
Authenticated as workspace: acme-data-team
3. Connect a source
Initialize your first pipeline with an interactive connector wizard:
Terminal
$ qv pipeline init orders-pipeline
Pipeline config written to .queryvine/pipelines/orders-pipeline.yaml
Schema fingerprint captured: 3 tables, 47 columns
4. Add drift rules
Queryvine created a drift_rules.yaml with sensible defaults. Open it to see what's detected automatically:
.queryvine/drift_rules.yaml
pipeline: orders-pipeline
drift_rules:
- type: column_rename
severity: critical
action: pause_and_alert
- type: type_widen
severity: warning
action: alert_continue
- type: column_drop
severity: critical
action: pause_and_alert
- type: column_add
severity: info
action: auto_migrate
5. Deploy and run
Push your pipeline to Queryvine and trigger the first run:
Terminal
$ qv pipeline deploy orders-pipeline
Deploying pipeline orders-pipeline...
Pipeline ID: pipe_7x9m2k4n
$ qv run start orders-pipeline
Batch 1/12 complete — 84,231 rows synced
Batch 12/12 complete — 1,029,831 rows total (847ms)
Pipeline run completed. Schema unchanged.
Your pipeline is live. Queryvine will now monitor every run for schema changes and alert you before data breaks.
What's next
- Schema drift reference — full list of drift types and YAML rule syntax
- DAG reference — multi-step pipelines, dependencies, backfill
- API reference — REST endpoints + webhook events
- All connectors — 50+ sources and destinations