Dagster

Solution

A table (or file, or report) you declare with its dependencies; the scheduler materializes it. You are not scheduling a Python function that happens to write a table — you are scheduling the table.

Solution

dbt tests grain and relationships in the warehouse. Asset checks are the orchestrator saying this materialization is not fit for downstream. Both. Checks without dbt leave SQL untested. dbt without checks leave a green DAG on an empty table.

Solution

A full rebuild of every downstream asset. Partitioned assets + targeted backfill. If your graph cannot backfill one day, it is a batch script wearing assets.

Solution

A large heterogeneous ops estate, vendor sensors, and a team already staffed on Airflow. Move when the DAG is secretly a data graph and assets would delete half the glue. Fashion is not a reason.

Solution

In a resource / I/O manager, not in the op. Same rule as Airflow connections. If the PR has a password, it fails the screen.

Solution

A typed asset with lineage, freshness policy, and a materialization history — not just a task log. The SQL can be the same. Dagster’s pitch is the graph of data, not the clock.

Solution

Silently skip, or overwrite 01-05. You materialize the 01-03 partition (backfill) without kicking the whole year. Partitioned assets exist so time is data, not a side effect.

Solution

dbt tests live with the SQL model; Dagster checks gate materialization in the orchestrator. Duplicate unique tests are noise. Pick one grain test as the page, the other as defense in depth.

Solution

No. Two orchestrators can be honest if ownership is split and you do not dual-schedule the same MERGE. A rewrite of every DAG is a year, not a sprint. Say the boundary.

Solution

In a Dagster resource / secret backend, not in the asset body. The IO manager writes parquet/Snowflake; the asset function should not open a raw connection with a hardcoded URL.

Solution

Maybe: the SLA was a hope. Either start earlier, slim the job, or set freshness to 09:30 and tell stakeholders. A policy that fires every day is a ignored alarm.