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

Hadoop QA commented on HBASE-8140:
----------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12574420/0001-HBASE-8140-addendum-add-test-category.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 4 new 
or modified tests.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/4898//console

This message is automatically generated.
                
> 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

Reply via email to