[
https://issues.apache.org/jira/browse/MAPREDUCE-4642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451332#comment-13451332
]
Hudson commented on MAPREDUCE-4642:
-----------------------------------
Integrated in Hadoop-Hdfs-trunk #1159 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/1159/])
MAPREDUCE-4642. MiniMRClientClusterFactory should not use job.setJar()
(rkanter via tucu) (Revision 1382093)
Result = FAILURE
tucu : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1382093
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapred/MiniMRClientClusterFactory.java
> MiniMRClientClusterFactory should not use job.setJar()
> ------------------------------------------------------
>
> Key: MAPREDUCE-4642
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4642
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: test
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Fix For: 2.0.2-alpha
>
> Attachments: MAPREDUCE-4642.patch, MAPREDUCE-4642.patch
>
>
> Currently, MiniMRClientClusterFactory does {{job.setJar(callerJar)}} so that
> the {{callerJar}} is added to the cache in MR2. However, this makes the
> resulting configuration inconsistent between MR1 and MR2 as in MR1 the job
> jar is not set and in MR2 its set to the {{callerJar}}. This difference can
> also cause some tests to fail in Oozie. We should instead use the
> {{job.addCacheFile()}} method.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
