[
https://issues.apache.org/jira/browse/AURORA-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Lambert updated AURORA-1093:
----------------------------------
Sprint: Twitter Aurora Q1'15 Sprint 2, Twitter Aurora Q1'15 Sprint 3 (was:
Twitter Aurora Q1'15 Sprint 2)
> Scheduler updates should be uniquely identified by jobKey + updateId
> --------------------------------------------------------------------
>
> Key: AURORA-1093
> URL: https://issues.apache.org/jira/browse/AURORA-1093
> Project: Aurora
> Issue Type: Story
> Components: Client, Scheduler, UI
> Reporter: Maxim Khutornenko
> Assignee: Bill Farner
>
> We should generalize the approach of dealing with scheduler updates by always
> uniquely identifying them by a new composite key that includes both jobKey
> and the updateId, e.g.:
> {noformat}
> struct JobUpdateKey {
> 1: JobKey jobKey
> 2: string updateId
> }
> {noformat}
> The above approach would benefit us long term when it comes to implementing a
> fully functional REST API. Having both job key and update ID components in
> the URL will help us logically split authorization and application data
> layers.
> E.g.: in {{/api/updates/role/env/name/updateId}} the {{/role/env/name}} may
> be used for authorization whereas the {{updateId}} will remove the ambiguity
> from the data lookup.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
