[
https://issues.apache.org/jira/browse/YUNIKORN-1965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig Condit resolved YUNIKORN-1965.
------------------------------------
Fix Version/s: 1.4.0
Target Version: 1.4.0
Resolution: Fixed
Merged to master.
> Display a unique id on the REST interface when returning events
> ---------------------------------------------------------------
>
> Key: YUNIKORN-1965
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1965
> Project: Apache YuniKorn
> Issue Type: Sub-task
> Components: core - scheduler
> Reporter: Peter Bacsko
> Assignee: Peter Bacsko
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.4.0
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
