How do I run Python transformations against Athena?
Bruin runs the whole pipeline against Athena 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 Parquet files written to S3 and registered in the Glue catalog and incremental assets use partition overwrite. 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
Athena + Bruin CLI
What you get
How to do it
- 1
Run bruin init and add a athena connection for Athena.
- 2
Declare an ingestion asset so raw data lands in Athena via Parquet files written to S3 and registered in the Glue catalog.
- 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 partition overwrite.
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 Athena and runs its checks before anything downstream reads it.
Worth knowing
On Athena, unpartitioned CSV in S3 is the most expensive possible layout; convert to partitioned Parquet
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 Athena 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 Athena pipeline. |
| SQLMesh | Strong on Athena with virtual environments that cut the compute cost of reviewing a change. Transformation only, so you still need ingestion. |
| Native Athena tooling | Staying inside Athena 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 Athena?
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 Athena. Loads use Parquet files written to S3 and registered in the Glue catalog.
Do I need an orchestrator to run Athena 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 Athena?
On Athena the main lever is partitioning and columnar files, because billing is per byte scanned. Incremental models using partition overwrite matter more than which tool you pick.
Related use cases
Run Python transformations on Snowflake
How do I run Python transformations against Snowflake?
Python transformationsRun Python transformations on BigQuery
How do I run Python transformations against BigQuery?
Python transformationsRun Python transformations on Databricks
How do I run Python transformations against Databricks?
One pipeline, end to end
Open source. Ingestion, SQL and Python transformations, and checks in one graph.