aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bhuvan Arumugam (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AURORA-84) Deprecate the Identity struct
Date Fri, 31 Oct 2014 21:42:35 GMT

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

Bhuvan Arumugam commented on AURORA-84:
---------------------------------------

https://reviews.apache.org/r/26394/
https://reviews.apache.org/r/26762/

The above fixes break client and scheduler, unless both of them are upgraded simultaneously.
See [AURORA-898#comment-14192533|https://issues.apache.org/jira/browse/AURORA-898?focusedCommentId=14192533]
for details

> Deprecate the Identity struct
> -----------------------------
>
>                 Key: AURORA-84
>                 URL: https://issues.apache.org/jira/browse/AURORA-84
>             Project: Aurora
>          Issue Type: Task
>          Components: Client, Scheduler
>            Reporter: Bill Farner
>            Assignee: Maxim Khutornenko
>             Fix For: 0.6.0
>
>
> The Identity field is nested in several structs, and the {{role}} field it contains is
~always redundant to a field in {{JobKey}}. Consider removing Identity and using (or adding)
a non-user-bearing field like JobKey.
> An open question is whether whether {{Identity.user}} should be retained.  Most likely
yes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message