Skip to content

Configure AutoMaterialization policy for multiple dbt assets #17882

Closed Answered by OwenKephart
dagsir[bot] bot asked this question in Q&A
Discussion options

You must be logged in to vote

When using AutoMaterializePolicy.eager() (or any policy with the materialize_on_parent_updated() rule), Dagster should attempt to group materializations into the same run (regardless of if the asset is from dbt or elsewhere).

Is it possible that the root assets in your graph are materializing at slightly different times, causing the materializations to be sort of "desynchronized"?

Do you have an example of this one-by-one execution that you can share?

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by rexledesma
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
integration: dbt Related to dagster-dbt area: declarative-automation Related to Declarative Automation, AutomationConditions and Auto Materialization
1 participant