[
https://issues.apache.org/jira/browse/AURORA-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15421240#comment-15421240
]
Maxim Khutornenko commented on AURORA-1711:
-------------------------------------------
I like the idea of the update metadata but don't like the part where scheduler
would be required to look into it. The metadata field should be a free-form (as
far as scheduler goes) string or key/value data storing any arbitrary values
provided by the client. Clients are free to interpret that data in the desired
way, including querying for active updates to enforce the uniqueness
requirements.
> Allow client to store metadata on Update entity
> -----------------------------------------------
>
> Key: AURORA-1711
> URL: https://issues.apache.org/jira/browse/AURORA-1711
> Project: Aurora
> Issue Type: Task
> Components: Scheduler
> Reporter: David McLaughlin
>
> I have a use case where I'm programmatically starting updates via the Aurora
> API and sometimes the request to the scheduler times out or fails, even
> though the update is written to storage and started.
> I'd like to be able to store some unique identifier on the update so that we
> can reconcile this state later. We can make this generic by allowing clients
> to store arbitrary metadata on an update (similar to how they do it with job
> configuration).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
