[jira] [Comment Edited] (AURORA-1711) Allow client to store metadata on Update entity

["Bill Farner (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AURORA-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15335225#comment-15335225 ] 

Bill Farner edited comment on AURORA-1711 at 6/17/16 2:16 AM:
--------------------------------------------------------------

What i'm not clear on is why the specific _request_ needs to be uniquely identified, since the operation is idempotent.  Idempotence guarantees that multiple clients can safely step on each other, provided they are trying to achieve the same state.  Does that make sense here, or am i off-base?

edit: s/instances/clients/ for clarity


was (Author: wfarner):
What i'm not clear on is why the specific _request_ needs to be uniquely identified, since the operation is idempotent.  Idempotence guarantees that multiple instances can safely step on each other, provided they are trying to achieve the same state.  Does that make sense here, or am i off-base?

> 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)