[
https://issues.apache.org/jira/browse/MAPREDUCE-4043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13236775#comment-13236775
]
Hadoop QA commented on MAPREDUCE-4043:
--------------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12519644/MAPREDUCE-4043.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 8 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed unit tests in .
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2091//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/2091//console
This message is automatically generated.
> 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, 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
