Description
Description
In Airflow 3, when using versioned DAG bundles, the DAG definition is serialized and associated with a DAG run at the time of its creation. This feature would enable changing that association to another available DAG version for a specific DAG run—or preferably for a group of runs—so that after clearing the DAG run, the updated definition, including any structural changes to the DAG, would be applied.
Use case/motivation
This feature would allow historical DAG runs to reload the updated DAG structure when clearing. Currently, if the DAG definition has changed (e.g., tasks have been added or removed), rerunning past DAG runs won't reflect those changes because task instances remain tied to the serialized DAG version that existed at the time they were originally created. While current behaviour might be desired and should remain as default, allowing to change DAG version associated to a DAG run would make it more flexible for Airflow operators.
Related issues
Are you willing to submit a PR?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project's Code of Conduct