hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Joseph Evans (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4043) Secret keys set in Credentials are not seen by tasks
Date Fri, 23 Mar 2012 20:45:28 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-4043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13237098#comment-13237098

Robert Joseph Evans commented on MAPREDUCE-4043:

I got word form Vinod that he is OK with the change, and I can go ahead and check it in. 
If there is anything else that comes up later it can be done in a follow on JIRA. So I will
put it in.
> Secret keys set in Credentials are not seen by tasks
> ----------------------------------------------------
>                 Key: MAPREDUCE-4043
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4043
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2, security
>    Affects Versions: 0.23.2
>            Reporter: Jason Lowe
>            Assignee: Jason Lowe
>            Priority: Blocker
>         Attachments: MAPREDUCE-4043.patch, MAPREDUCE-4043.patch
> The following scenario works in 0.20.205 but no longer works in 0.23:
> 1) During job submission, a secret key is set by calling jobConf.getCredentials().addSecretKey(Text,
> 2) A map task retrieves the secret key by calling jobConf.getCredentials().getSecretKey(Text)
> In 205 the secret key is retrieved successfully but in 0.23 the secret key is missing.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message