[
https://issues.apache.org/jira/browse/HADOOP-9426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13613325#comment-13613325
]
Enis Soztutar commented on HADOOP-9426:
---------------------------------------
bq. Do we really want this kind of functionality being part of Hadoop public
API?
Yes. MR and some yarn applications need the ability to ship jars to the
cluster, and make it available for it's tasks. There is only limited support to
set the jars through Job.setJarByClass(), but 1. This is MR specific, 2. This
will only ship your main jar, not dependent jars, unless you are doing the
uber-jar which is pretty inconvenient.
We need to be able to say to ship these jars, OR make these classes available.
> 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
> Reporter: Nick Dimiduk
> Attachments: 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
