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

Nick Dimiduk commented on HADOOP-9426:
--------------------------------------

Transitive dependency resolution would be awesome 
([aether|https://github.com/sonatype/sonatype-aether], anyone?). However, it's 
well beyond the scope of this addition. For the purposes of HBase, we expect 
the user to itemize representative classes from all the jars needed by their 
job, so that burdon is on the user already. In this case, the jar doesn't 
actually exist, it's been extracted by a previous jobstep's runtime. We use 
JarFinder to package it back up again and pass it along to the next job.
                
> Hadoop should expose Jar location utilities on its public API
> -------------------------------------------------------------
>
>                 Key: HADOOP-9426
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9426
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 1.0.0, 1.1.0, 2.0.0-alpha
>            Reporter: Nick Dimiduk
>         Attachments: 
> 0001-HADOOP-9426-Promote-JarFinder-out-of-test-jar.patch, 
> 0001-HADOOP-9426-Promote-JarFinder-out-of-test-jar.patch
>
>
> The facilities behind JobConf#setJarByClass and the JarFinder utility in test 
> are both generally useful. As the core platform, these should be published as 
> part of the public API. In addition to HBase, they are probably useful for 
> Pig and Hive as well. See also HBASE-2588, HBASE-5317, HBASE-8140.

--
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