Rename DagRun queue state to avoid confusion with TaskInstance
- Dominant language
- Python
- Stars
- 46.9k
- Forks
- 17.8k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 483
Description
### Body
Currently both DagRun and TaskInstance use queue as state (which is not related one to another at all)
I find that this is very confusing! because Queue DagRun actually means that the DagRun didn’t even start while queue task means it passed the scheduler and waiting for worker slot.
My suggestion simply not to use the same string (queue) to describe the different meaning.
(*) We also use Running for both DagRuns/tasks but I find this specific one less confusing as it actually means quite the same (something in worker is being executed).
Slack thread: https://apache-airflow.slack.com/archives/CCPRP7943/p1653990216805099
### Committer
- [X] I acknowledge that I am a maintainer/committer of the Apache Airflow project.
Contributor guide
Research direction
Start by tracing where DagRun and TaskInstance states are defined and where their queue labels are displayed or consumed. Decide on a distinct DagRun label, then update the affected state references and verify that DagRun and TaskInstance status displays no longer use the same wording.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, data-engineering
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100