[ 
https://issues.apache.org/jira/browse/HADOOP-9989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13773565#comment-13773565
 ] 

Jinghui Wang commented on HADOOP-9989:
--------------------------------------

Based on how JobSubmitter process the value of the 
mapreduce.job.credentials.json key, the tokenCacheFile passed in with the 
command line should be a JSON file, which makes sense as the 
GenericOptionsParser reads the value of this file and set it to the 
mapreduce.job.credentials.json in the configuration originally. Attached patch 
is based on the assumption that the tokenCacheFile is a JSON file.
                
> Bug introduced in HADOOP-9374, which parses the -tokenCacheFile as binary 
> file but set it to the configuration as JSON file.
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-9989
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9989
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: security, util
>    Affects Versions: 2.1.0-beta
>         Environment: Red Hat Enterprise 6 with Sun Java 1.7 and IBM Java 1.6
>            Reporter: Jinghui Wang
>             Fix For: 3.0.0, 2.1.1-beta
>
>         Attachments: HADOOP-9989.patch
>
>
> The code in JIRA HADOOP-9374's patch introduced a bug, where the value of the 
> tokenCacheFile parameter is being parsed as a binary file and set it to the
> mapreduce.job.credentials.json parameter in GenericOptionsParser, which 
> cannot be parsed by JobSubmitter when it gets the value.

--
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

Reply via email to