[
https://issues.apache.org/jira/browse/AURORA-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14173136#comment-14173136
]
Maxim Khutornenko commented on AURORA-84:
-----------------------------------------
Again, we should not put userId into TaskConfigs. That will prevent clean
client diffs when run by different users against the same job. It will also add
to SQL TaskStore (when we have one) duplication when multiple updates of the
same job are completed by different users (e.g. users change instance counts
only without modifying underlying task configs). The desired solution should
probably include a new UserStore where individual entries would link over to
TaskStore config IDs.
> 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)
