dagster: dbt assets get incorrectly materialized by multiple dbt runs

Dagster version

1.2.3

What’s the issue?

I’m on dagster-dbt 0.18.3 and load my dbt project with load_assets_from_dbt_project.

When triggering dbt asset materializations from Dagit. Dependent dbt assets sometimes get built in independent ops.

What did you expect to happen?

I use software-defined dbt assets. I want to trigger a run by selecting dbt assets on the Dagit UI.

I clicked “Materialize All” on this screen. Since these assets are all defined in a single dbt project and depend on each other, I expect Dagster to trigger a single dbt run with all assets listed.

Instead, Dagster breaks up the job into 2 ops. One builds a single asset, while the other builds everything else. It’s incorrect because the orphaned asset should be built after its dependencies are materialized.

How to reproduce?

No response

Deployment type

Dagster Helm chart

Deployment details

No response

Additional information

No response

Message from the maintainers

Impacted by this issue? Give it a 👍! We factor engagement into prioritization.