[
https://issues.apache.org/jira/browse/MAPREDUCE-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13705094#comment-13705094
]
Sandy Ryza commented on MAPREDUCE-5379:
---------------------------------------
Implementing this, I'm starting to see the difficulty. The trouble I'm facing
is that TokenCache#obtainTokensFromNamenode gets called from a lot of different
places (and possibly user code) so we don't have an easy way of determining
which tokens were added from it. We could possibly have a static collection in
TokenCache that tracks this. But this seems somewhat ugly, and users could get
around it if they wanted to. Would there be issues with including _all_ of the
tokens that end up in a job.getCredentials()?
> 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
>
> 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
