Details
-
Sub-task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
Description
When the scheduler is restarted, ID are always counted from 0, which makes IDs not unique. If someone decides to store the events in the database with IDs being a primary key, it will not be possible because of this.
We should expose extra information to the REST API so that event IDs become unique when they are concatenated. For example:
- Start timestamp
- Random number
- Random UUID
- An ID constructed from the pod's unique ID
- etc.
Attachments
Issue Links
- links to