aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Farner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AURORA-1093) Scheduler updates should be uniquely identified by jobKey + updateId
Date Tue, 24 Feb 2015 23:48:04 GMT

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

Bill Farner commented on AURORA-1093:
-------------------------------------

https://reviews.apache.org/r/31388/

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

Mime
View raw message