hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alejandro Abdelnur (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9989) Bug introduced in HADOOP-9374, which parses the -tokenCacheFile as binary file but set it to the configuration as JSON file.
Date Fri, 12 Sep 2014 17:25:35 GMT

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

Alejandro Abdelnur commented on HADOOP-9989:
--------------------------------------------

also, is possible to use non-local FS URIs?  if so, then the code does not handle that currently,
right?

> 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
>            Assignee: zhihai xu
>             Fix For: 2.6.0
>
>         Attachments: HADOOP-9989.001.patch, HADOOP-9989.addendum0.patch, HADOOP-9989.patch
>
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message