[jira] [Commented] (MAPREDUCE-4043) Secret keys set in Credentials are not seen by tasks

["Jason Lowe (Commented) (JIRA)" <ji...@apache.org>]

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

Jason Lowe commented on MAPREDUCE-4043:
---------------------------------------

The tasks can workaround the problem by reading the appTokens file that was pushed to HDFS when the job was launched.  For example:

{code}
    Credentials cred = Credentials.readTokenStorageFile(new Path(jobConf.get("mapreduce.job.dir"), "appTokens"), jobConf);
    byte[] secretKey = cred.getSecretKey(SECRET_KEY_ALIAS);
{code}
                
> 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: contrib/streaming, mrv2
>    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, byte[])
> 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