[
https://issues.apache.org/jira/browse/AURORA-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David McLaughlin updated AURORA-1711:
-------------------------------------
Description:
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).
was:
I have a use case where I'm programmatically starting updates programmatically
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).
> 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)
