[
https://issues.apache.org/jira/browse/HADOOP-9426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13633561#comment-13633561
]
Alejandro Abdelnur commented on HADOOP-9426:
--------------------------------------------
bq. 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?
If you use the parent job conf to create your child job you'll get the
distributed cached config for free.
For example, in Oozie's case we populate the jobconf for child job in the oozie
server and copy it to HDFS for the parent to loaded and add it to the child
jobconf it is creating (actually oozie server cooks up the full job conf for
the child job, the parent job just loads and uses it for the submission).
> 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
