[ https://issues.apache.org/jira/browse/MAPREDUCE-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13182171#comment-13182171 ]
Hadoop QA commented on MAPREDUCE-3380: -------------------------------------- +1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12509817/MAPREDUCE-3380.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 15 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/1565//testReport/ Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1565//console This message is automatically generated. > Token infrastructure for running clients which are not kerberos authenticated > ----------------------------------------------------------------------------- > > Key: MAPREDUCE-3380 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3380 > Project: Hadoop Map/Reduce > Issue Type: Sub-task > Components: mr-am, mrv2 > Affects Versions: 0.23.0 > Reporter: Alejandro Abdelnur > Assignee: Mahadev konar > Priority: Blocker > Fix For: 0.23.1 > > Attachments: MAPREDUCE-3380.branch-0.23.patch, > MAPREDUCE-3380.branch-0.23.patch, MAPREDUCE-3380.patch, MAPREDUCE-3380.patch, > MAPREDUCE-3380.patch, MAPREDUCE-3380.patch, MAPREDUCE-3380.patch, > MAPREDUCE-3380_v1.patch > > > The JobClient.getDelegationToken() method is returning NULL, this makes Oozie > fail when trying to get the delegation token to use it for starting a job. > What is seems to be happing is that Jobclient.getDelegationToken() calls > Cluster.getDelegationToken() that calls YarnRunner.getDelegationToken() that > calls ResourceMgrDelegate.getDelegationToken(). And the last one is not > implemented. (Thanks Ahmed for tracing this in MR2 code) -- 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