hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-4043) Secret keys set in Credentials are not seen by tasks
Date Wed, 21 Mar 2012 17:33:41 GMT

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

Vinod Kumar Vavilapalli commented on MAPREDUCE-4043:

Can you please check and see if the patch for MAPREDUCE-3727 is the cause? I remember something
like this, credentials being removed from the client as one of the proposals there. Don't
have bandwidth to confirm this myself. Thanks.
> 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
>            Priority: Blocker
> 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