Configure AutoMaterialization policy for multiple dbt assets #17882
-
Hi all, quick question: Is it possible to configure an AutoMaterialization policy for multiple dbt assets at once? Context: When run thorough a job, dbt assets are materialized in the same run (handled by dbt), but if I configure AutoMaterialization policies for each dbt asset, they are materialized one by one. I know I can configure a sensor+job combo, but was search for a cleaner solution. The question was originally asked in Dagster Slack. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
When using 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? |
Beta Was this translation helpful? Give feedback.
When using
AutoMaterializePolicy.eager()
(or any policy with thematerialize_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?