Solve for when dag is in a versioned bundle, user tries to clear a 2.x-generated dag run
- Dominant language
- Python
- Stars
- 46.9k
- Forks
- 17.8k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 483
Description
### Body
After upgrade, if a dag is in a versioned bundle, the existing dag runs will not have dag versions.
So, what version to use when we clear an old one?
According to Jed, we should probably set the version to whatever the current version is and run with that.
**I am not sure what the current behavior is.** If this is already the current behavior, just close this ticket.
### Committer
- [x] I acknowledge that I am a maintainer/committer of the Apache Airflow project.
Contributor guide
Research direction
No file, test, or entry point is identified. First reproduce the upgrade scenario with a versioned bundle and an existing 2.x-generated DAG run, then trace the clear operation's version handling. Done means confirming the current behavior and, if needed, defining a tested rule for the version used when clearing the old run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100