[
https://issues.apache.org/jira/browse/MAPREDUCE-1250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12792096#action_12792096
]
Kan Zhang commented on MAPREDUCE-1250:
--------------------------------------
> I think it may make more sense to store a Token in the Task, especially since
> it is Writable and can be easily serialized as part of the Task's write
> method.
Currently, it only servers as a temporary in-memory cache for the SecretKey (to
avoid converting from tokenPassword to SecretKey each time the token is used
for Shuffle). The token itself is not intended to be serialized and sent along
with the Task object. The passing of credentials for a Task is handled by way
of the credential cache. If we're going to pass credentials along with Task
objects, we need to make sure Task objects are handled properly. Since this is
a re-factoring patch, I suggest we evaluate it as part of the credential cache
work Boris is doing.
Attaching a patch that addressed your other comments.
> Refactor job token to use a common token interface
> --------------------------------------------------
>
> Key: MAPREDUCE-1250
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1250
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: security
> Reporter: Kan Zhang
> Assignee: Kan Zhang
> Attachments: m1250-09.patch
>
>
> The idea is to use a common token interface for both job token and delegation
> token (HADOOP-6373) so that the RPC layer that uses them don't have to
> differentiate them.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
