Unique task identifier across all task runs/dag runs/retries. #45447
Unanswered
corkienjoyer
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello guys,
I'm trying to find a way to uniquely identify the task run between all the dag runs and retries (this is needed for me to pass to an external system). I've checked the TaskInstance model implementation and saw that the uniqueness of the task is defined with a composite key of 4 primary keys. Combining them creates that unique identifier for me which works just fine - the only problem is that it's very unreadable.
Is there another way of finding that uniqueness between the task runs? I've stumbled upon the job_id column but I cannot seem to find any description related to it - not sure if this can be somehow used to solve my problem.
Any suggestions?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions