Hey! ```class CustomDagsterDbtTranslator(DagsterD...
# integration-dbt
a
Hey!
Copy code
class CustomDagsterDbtTranslator(DagsterDbtTranslator):
    @classmethod
    def get_auto_materialize_policy(
        cls, dbt_resource_props: Mapping[str, Any]
    ) -> Optional[AutoMaterializePolicy]:
        return AutoMaterializePolicy.eager().with_rules(
            AutoMaterializeRule.materialize_on_missing(),
            AutoMaterializeRule.materialize_on_parent_updated(),
        )
We have above
dagster_dbt_translator
for
load_assets_from_dbt_project
and defined schedule for certain assets. But auto materialization isn't being triggered for downstream dbt assets. How can we debug further into it?
🤖 1
c
Hi Ashish. Some areas you can troubleshoot: • In the UI, can you verify auto materialize policies exist for the assets as expected? • Can you verify that the auto-materialize daemon is turned on? • In the UI, there's an auto-materialize history page for each asset. This contains historic evaluation data, which shows reasons why a materialization/skip happened:
a
Claire, thanks for the input! auto-materialize daemon wasn't ON, I just enabled it.
But I can't see "Auto-materialize history" tab on any of the assets.
Hm, maybe we don't show "Auto-materialize history" if policy isn't attached to an asset
Next I need to figure out whether policy is being attached properly or not.
Hm hm, it seems to be a bug in the library. https://github.com/dagster-io/dagster/blob/b453aa33badb333bef03cce96c424f4ac4b6915[…]python_modules/libraries/dagster-dbt/dagster_dbt/asset_utils.py doesn't take`dagster_dbt_translator.get_auto_materialize_policy` into consideration. CC - @claire
Same goes for
get_freshness_policy
I guess.
r
Thanks for the report, should be resolved by https://github.com/dagster-io/dagster/pull/16373