Distinguish between marking failure/success by user and by task #33581
Replies: 6 comments
-
Thanks for opening your first issue here! Be sure to follow the issue template! |
Beta Was this translation helpful? Give feedback.
-
Sounds like an interesting feature. Maybe you would like to add it @guidopetri ? |
Beta Was this translation helpful? Give feedback.
-
I'm not sure I have the required knowledge for that. There's an enum of task states here, which we could add to, but that would imply changing the marking mechanism to e.g. |
Beta Was this translation helpful? Give feedback.
-
Understood - maybe someone will pick it up then if there is an interest. |
Beta Was this translation helpful? Give feedback.
-
The concept of adding explicit status per each possible action is dangerous. When start this you will never hear the end of it. |
Beta Was this translation helpful? Give feedback.
-
@potiuk , I would like to work on this, can you please assign this ticket to me? |
Beta Was this translation helpful? Give feedback.
-
Description
Tasks should have a marker on them or additional information showing that they were marked success/failure/run/cleared by hand vs by the scheduler/worker processes.
Use case/motivation
When working with others on Airflow DAGs, we constantly have to keep in communication as to what we marked succeeded/failed because otherwise it is not clear whether a task succeeded/failed "naturally" as per the task or "artificially" as being marked as such by a user.
It would be nice to have a difference between the two states, or a marker of some sort to identify that a task was succeeded/failed by hand.
Related issues
No response
Are you willing to submit a PR?
Code of Conduct
Beta Was this translation helpful? Give feedback.
All reactions