[
https://issues.apache.org/jira/browse/MAPREDUCE-5379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13706019#comment-13706019
]
Sandy Ryza commented on MAPREDUCE-5379:
---------------------------------------
bq. If the goal is traceability from a token to a job, how do you plan to
handle clients that lie or jobs that fail to propagate the conf value to a
subjob?
We are assuming that client code is trusted and that subjobs will be tracked
separately. Even if this does not cover all the cases, it is still useful.
bq. The core objection is the identifier must be opaque to the client.
After talking with Alejandro, I am only suggesting writing each token's kind,
service, and sequence number. This should be enough to associate with what's
logged in HDFS-4680. Are these meant to be opaque as well?
> 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.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
