[
https://issues.apache.org/jira/browse/HBASE-8140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13607143#comment-13607143
]
Hudson commented on HBASE-8140:
-------------------------------
Integrated in HBase-TRUNK #3975 (See
[https://builds.apache.org/job/HBase-TRUNK/3975/])
HBASE-8140 TableMapReduceUtils#addDependencyJar fails when nested inside
another MR job -- ADDENDUM (Revision 1458545)
HBASE-8140 TableMapReduceUtils#addDependencyJar fails when nested inside
another MR job (Revision 1458531)
Result = FAILURE
stack :
Files :
*
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/hadoopbackport/TestJarFinder.java
stack :
Files :
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/TableMapReduceUtil.java
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/hadoopbackport
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/hadoopbackport/JarFinder.java
*
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/hadoopbackport
*
/hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/hadoopbackport/TestJarFinder.java
> TableMapReduceUtils#addDependencyJar fails when nested inside another MR job
> ----------------------------------------------------------------------------
>
> Key: HBASE-8140
> URL: https://issues.apache.org/jira/browse/HBASE-8140
> Project: HBase
> Issue Type: Bug
> Components: mapreduce
> Reporter: Nick Dimiduk
> Assignee: Nick Dimiduk
> Fix For: 0.95.0, 0.98.0, 0.94.7
>
> Attachments: 0001-HBASE-8140-addendum-add-test-category.patch,
> 8140-port-jarfinder-0.94.patch, 8140-port-jarfinder-trunk.patch
>
>
> TableMapReduceUtils#addDependencyJar is used when configuring a mapreduce job
> to make sure dependencies of the job are shipped to the cluster. The code
> depends on finding an actual jar file containing the necessary classes. This
> is not always the case, for instance, when run at the end of another
> mapreduce job. In that case, dependency jars have already been shipped to the
> cluster and expanded in the parent job's run folder. Those dependencies are
> there, just not available as jars.
--
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
