Apache Airflow version
main (development)
If "Other Airflow 3 version" selected, which one?
No response
What happened?
Materialising an asset via UI creates dagrun type of runTypes.asset_materialization
Materialising an asset via CLI creates dagrun type of manual
What you think should happen instead?
Dagrun via both ways should be uniform.
How to reproduce
- Start airflow instance on main branch, make sure we have assets available.
- Materialise an asset which has single upstream dag via UI, notice upstream dag has
runTypes.asset_materialization type dagrun.
- Materialise same asset now via CLI by running command
airflow assets materialize --uri <asset_uri>, notice upstream dag has manual type dagrun.
Operating System
Linux
Versions of Apache Airflow Providers
No response
Deployment
Other
Deployment details
No response
Anything else?
No response
Are you willing to submit PR?
Code of Conduct
Apache Airflow version
main (development)
If "Other Airflow 3 version" selected, which one?
No response
What happened?
Materialising an asset via UI creates dagrun type of
runTypes.asset_materializationMaterialising an asset via CLI creates dagrun type of
manualWhat you think should happen instead?
Dagrun via both ways should be uniform.
How to reproduce
runTypes.asset_materializationtype dagrun.airflow assets materialize --uri <asset_uri>, notice upstream dag hasmanualtype dagrun.Operating System
Linux
Versions of Apache Airflow Providers
No response
Deployment
Other
Deployment details
No response
Anything else?
No response
Are you willing to submit PR?
Code of Conduct