You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2022/06/09 14:42:03 UTC

[GitHub] [airflow] ei-grad commented on issue #24045: Rename DagRun queue state to avoid confusion with TaskInstance

ei-grad commented on issue #24045:
URL: https://github.com/apache/airflow/issues/24045#issuecomment-1151210645

   When the task is waiting for worker it is also "didn't even start" in terms of operator execution.
   
   In my experience it is always tricky to get the logic of scheduled/queued TI for the new people, but there was no problems with the DagRun states naming. To disagree with the slack thread - for the data engineer familiar with airflow internals there is no such confusion, or at least it doesn't seem to be critical enough to break the UX (for the data engineers too).


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org