[
https://issues.apache.org/jira/browse/AURORA-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14173128#comment-14173128
]
Kevin Sweeney commented on AURORA-84:
-------------------------------------
It's not useless either - that field will always be present with running tasks
in the system, part of scheduler backups, etc. The scheduler logs are much
better suited to forensics (e.g. finding someone who was creating / deleting
malicious jobs on the cluster at an interval to evade backups), but the
presence in the thrift structure is more useful for the hopefully more common
use case of finding a user to contact about a running job.
> 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)
