aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maxim Khutornenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AURORA-84) Deprecate the Identity struct
Date Mon, 20 Oct 2014 19:49:34 GMT

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

Maxim Khutornenko commented on AURORA-84:
-----------------------------------------

{quote}
It seems risky to break ground on deprecating Identity without the replacement plan in place
{quote}
I am confused. Replacement to what exactly? The user field is not currently used anywhere
as far as I can see. What's the risk?

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