https://flyte.org logo
Join Slack
Powered by
I was hoping to find out how Flyte manages uniquen...
# flytekit
g
I was hoping to find out how Flyte manages uniqueness of execution_ids. Can we assume that execution_ids will be unique within a Flyte project?
y
yeah, at least within project/domain.
k
@Govind Raghu you can also create your own execution names
this can be useful for idempotency
d
wait really?
that might be really useful
cc @Varun Kulkarni
k
ohh you did not know that?
cc @Alekhya / @Smriti Satyan can we please document this behavior.
👍 1
Every execution that a user launches has optional 
name
- field. If the name field is specified, that is used as a de-dupe identifier (for idempotency). Extremely useful if you are running workflows programmatically and want to safeguard against potential network errors etc. It is safe to re-execute with the same name. An AlreadyExists error will be returned. If you do not provide the name, flyteadmin will generate one for you
d
does this propogate to sub launch plans?
k
@Dylan Wilder - by definition yes right? If the parent never gets relaunched, all sub will never get relaunched right
also all sub are always launched deterministically, where the input execution id and the node id are important factors
d
wait are we talking about the same thing? do child lp's get the parent exec name? because if you don't specify they do not
or is name different than id?
k
its a different id
but its derived from the parents name deterministically
you cannot get the same name, because execution-ids are unique within the project+domain
is there somethign that you guys are looking for?
a
Sure Ketan. Will look into documenting it.
d
a way to track sub executions across flyte events
k
Ohh interesting
In workflow execution event?
167 Views
Open in Slack
PreviousNext
Powered by