What's the issue?
How can I prevent that downstream assets are kicked off when the dbt asset is failing an asset check? As you can see the downstream (dbt) asset is NOT executed as desired. However, the python asset IS executed. How can I ensure the python asset is NOT executed? The definition of the python dummy asset looks like:
@asset(
compute_kind="python",
group_name="logistics",
deps=[get_asset_key_for_model([unpartitioned_assets], "my_first_dbt_model")],
)
def logistics_example():
https://imgur.com/a/eKqdPXS
b0f63526-7b09-4c3b-8a2f-a723dd1cdd6c.gz
What did you expect to happen?
I would expect to have the dbt asset check blocking
How to reproduce?
No response
Dagster version
1.8
Deployment type
Dagster Cloud
Deployment details
No response
Additional information
No response
Message from the maintainers
Impacted by this issue? Give it a 👍! We factor engagement into prioritization.
By submitting this issue, you agree to follow Dagster's Code of Conduct.
What's the issue?
How can I prevent that downstream assets are kicked off when the dbt asset is failing an asset check? As you can see the downstream (dbt) asset is NOT executed as desired. However, the python asset IS executed. How can I ensure the python asset is NOT executed? The definition of the python dummy asset looks like:
https://imgur.com/a/eKqdPXS
b0f63526-7b09-4c3b-8a2f-a723dd1cdd6c.gz
What did you expect to happen?
I would expect to have the dbt asset check blocking
How to reproduce?
No response
Dagster version
1.8
Deployment type
Dagster Cloud
Deployment details
No response
Additional information
No response
Message from the maintainers
Impacted by this issue? Give it a 👍! We factor engagement into prioritization.
By submitting this issue, you agree to follow Dagster's Code of Conduct.