[
https://issues.apache.org/jira/browse/HADOOP-9426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619959#comment-13619959
]
Alejandro Abdelnur commented on HADOOP-9426:
--------------------------------------------
Bobby, your last comment hit the nail. JarFinder is meant for testing, to be
able to find the JAR of class and, if necessary, create a JAR on the fly
containing all the classes in the specified class classpath location, typically
target/test-classes/*. This allows you to easily prepare a JAR for setting in
the jobconf when doing testing.
And, using the JarFinder with classes that are in JARs assumes you'll know all
the transitive dependencies JARs an specific classes from those transitive
dependencies to get all the JARs.
If an application wants to do that, it is fine with me (Oozie does this), I
would just not like Hadoop providing an API to do such thing which is quite
error prone.
> 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
