[
https://issues.apache.org/jira/browse/HADOOP-9426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619880#comment-13619880
]
Robert Joseph Evans commented on HADOOP-9426:
---------------------------------------------
[~tucu00], The reason for putting this functionality in is because now that
YARN is gaining traction there are more and more tools that run on top of YARN
that want this ability, similar to how Map/Reduce uses it. Yes -libjars is a
great way to ship dependencies for Map/Reduce, but MR also exposes this through
other interfaces and for non-mapreduce tools it would be nice to have this
functionality in a common place. I am not sure that hadoop-common is the best
place for this. yarn might be a better place, but I think common is an OK
place.
> 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
