[
https://issues.apache.org/jira/browse/MAPREDUCE-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13722469#comment-13722469
]
Daryn Sharp commented on MAPREDUCE-5379:
----------------------------------------
Alejandro and I discussed offline how decoding the token identifier will cause
incompatibility if the token identifier format is changed (ex. to a protobuf).
The client will fail to decode. Likewise for heterogenous clusters with
different token formats. Today, that won't be a problem because the client
treats the identifier as opaque bytes.
I provided Alejandro a sample patch that adds a trackingId into the token in a
backwards compatible manner, which uses the job id for tracking. It will
provide a more natural forward mapping in the audit logs.
> Include FS delegation token ID in job conf
> ------------------------------------------
>
> Key: MAPREDUCE-5379
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5379
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: job submission, security
> Affects Versions: 2.1.0-beta
> Reporter: Sandy Ryza
> Assignee: Sandy Ryza
> Attachments: MAPREDUCE-5379-1.patch, MAPREDUCE-5379.patch
>
>
> Making a job's FS delegation token ID accessible will allow external services
> to associate it with the file system operations it performs.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
