How do I build an end-to-end data pipeline on BigQuery?
Bruin runs the whole pipeline against BigQuery from one project: ingestion, SQL and Python transformations, and quality checks are all assets in the same dependency graph, so bruin run resolves the order and executes them in sequence. Loads use a native load job from GCS and incremental assets use MERGE on a primary key. The alternative is assembling an ingestion tool, a transformation framework, and an orchestrator, which works but leaves you owning the glue between them.
Command
bruin runDefined in
SQL + Python + YAML
Works with
BigQuery + Bruin CLI
What you get
How to do it
- 1
Run bruin init and add a bigquery connection for BigQuery.
- 2
Declare an ingestion asset so raw data lands in BigQuery via a native load job from GCS.
- 3
Add a SQL asset that models the raw table, with depends naming its upstream.
- 4
Declare column checks on the keys and amounts that matter.
- 5
Run bruin validate to confirm the graph resolves, then bruin run.
- 6
Schedule it in CI or Bruin Cloud, and switch heavy assets to MERGE on a primary key.
How it works in code
/* @bruin
name: mart.orders
materialization:
type: table
depends: [raw.orders]
columns:
- name: order_id
checks:
- name: unique
@bruin */
SELECT order_id, customer_id, order_total
FROM raw.ordersRun bruin run and Bruin builds the asset on BigQuery and runs its checks before anything downstream reads it.
Worth knowing
On BigQuery, a query that does not filter on the partition column scans the whole table and the partitioning buys you nothing
Other ways to do this
Bruin is not always the right answer. Here is where the alternatives are stronger.
| Option | When it is the better choice |
|---|---|
| Bruin | Build and run a complete BigQuery pipeline with Bruin: ingest, transform in SQL or Python, and check the output, all from one project. |
| dbt + Fivetran + Airflow | The conventional split. Mature and well documented, but three tools to run and integrate for one BigQuery pipeline. |
| SQLMesh | Strong on BigQuery with virtual environments that cut the compute cost of reviewing a change. Transformation only, so you still need ingestion. |
| Native BigQuery tooling | Staying inside BigQuery avoids another vendor, at the cost of portability if you ever move warehouse. |
Common questions
How do I build an end-to-end data pipeline on BigQuery?
Define each stage as an asset in one project and let the framework resolve the order. With Bruin, ingestion, SQL and Python transformations, and quality checks are all assets, and bruin run executes the graph against BigQuery. Loads use a native load job from GCS.
Do I need an orchestrator to run BigQuery pipelines?
Not for a straightforward pipeline. bruin run resolves dependencies itself, so a CI runner on a schedule is enough. A dedicated orchestrator earns its keep once you need complex retries, backfills, and cross-team scheduling.
What is the cheapest way to run pipelines on BigQuery?
On BigQuery the main lever is partitioning and clustering, because on-demand billing is per byte scanned. Incremental models using MERGE on a primary key matter more than which tool you pick.
Related use cases
Build an end-to-end data pipeline on Snowflake
How do I build an end-to-end data pipeline on Snowflake?
End-to-end pipelinesBuild an end-to-end data pipeline on Databricks
How do I build an end-to-end data pipeline on Databricks?
End-to-end pipelinesBuild an end-to-end data pipeline on Postgres
How do I build an end-to-end data pipeline on Postgres?
One pipeline, end to end
Open source. Ingestion, SQL and Python transformations, and checks in one graph.