[
https://issues.apache.org/jira/browse/AURORA-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14177475#comment-14177475
]
Maxim Khutornenko commented on AURORA-84:
-----------------------------------------
IMO, this point is moot given that: (a) we don't need this data often (if ever)
and (b) the fact that we already have a way to satisfy debugging needs with
scheduler logs recording every user RPC call.
On the other side, keeping the {{Identity}} blows up the size of our de-duped
snapshots and requires workarounds like AURORA-520.
> 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)
