R Lucas04/30/2023, 10:05 AM
, we used
to ensure reconciliation/automaterialize runs follows our run tags concurrency limits. I do not see how to do something similar with AutoMaterializePolicy.
sandy05/01/2023, 10:07 PM
Other question regarding reconciliation sensor and freshness policy: how can I enforce child asset with Freshness policy are rematerialized if any parent asset has changed ?Have you had a chance to look at the docs? https://docs.dagster.io/concepts/assets/asset-auto-execution Basically, if you use an eager AutoMaterializePolicy, it will do it immediately, not based on the freshness policies.
R Lucas05/02/2023, 6:22 AM
this will be possible in our upcoming release this week: https://docs.dagster.io/master/concepts/assets/asset-auto-execution#run-tags (link is to unreleased docs)@sandy from this documentation it seems like run tags can be set in
file which means that these tags would be global to all auto_materialize policies. Am I misunderstanding this or can auto_materialize runs be triggered by asset_reconciliation_sensor and associated run tags ?
sandy05/02/2023, 3:08 PM
from this documentation it seems like run tags can be set inso your issue is that you want different concurrency limits for different assets?file which means that these tags would be global to all auto_materialize policies.
R Lucas05/02/2023, 3:17 PM