[
https://issues.apache.org/jira/browse/HADOOP-9426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13622625#comment-13622625
]
Nick Dimiduk commented on HADOOP-9426:
--------------------------------------
For the usecase I'm concerned about, the jars were shipped to the cluster and
expanded via the parent job's use of the -tmpjars feature. The child job is
launched from the context of that parent job, where it sees classes from the
expanded jars, but not the jars themselves, available in the local fs tmp
working directory. Hence the use of JarFinder.
Are you suggesting that the parent process could locate the original jars in
the distributed cache and use them? This is an acceptable solution from the
HBase perspective. How might I resolve the paths?
I don't know if it resolves [~revans2]'s needs.
All I really care about is that Hadoop provide APIs to easily resolve a jar
path from a unique identifier of some kind (class-name, jar base-name, &c). If
that's done through JarFinder's repackaging or some other construct, I'm
largely ambivalent. HBase was already using JarFinder for some code-paths, so
it made sense to extend its use.
Please advise.
> 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
