Why aren’t job ID s standard UUID?
When we create a job using runpod the returned job ID is not a standard UUID. Instead, it’s some UUID with some suffix. I would like to know the reason for this, and also how to standardize the job IDs.
The reason for me to want this is because in our database we store the job ID but it violates UUID constraint
7 Replies
Unknown User•6mo ago
Message Not Public
Sign In & Join Server To View
Yes
Unknown User•6mo ago
Message Not Public
Sign In & Join Server To View
If it helps, you can't even use that ID with us after thirtyish minutes unless you ask support who can view metadata about it for 2 weeks. I would just recommend generating your own UUIDs and saving ours as a string
Unknown User•6mo ago
Message Not Public
Sign In & Join Server To View
I don't know enough about the uuid format to know what it signifies just that "it's important".
If the goal is to use it as a unique ID, you can probably just do that. But if the goal is to save a "Runpod job ID" id both advise against it because they don't have long lifetimes and say keep it as a string and make your own for the pkey
the job IDs used to be UUID only, about a year ago we added a suffix to shard where the actual job is located, moving forward treat the job IDs as a string