[
https://issues.apache.org/jira/browse/HBASE-9165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13823125#comment-13823125
]
Nick Dimiduk commented on HBASE-9165:
-------------------------------------
Yikes, I didn't realize the list of classes are different between the two. This
is a bug, right? Mapred is just a pass-through to the mapreduce implementations.
Zookeeper and protobuf jars are drawn by the same class in both cases. The same
Guava jar is brought in by Function.class and ImmutableSet.class respectively.
Not including the hbase.jar is a bug as reported by HBASE-9112, and fixed
inadvertently by HBASE-8146.
So yes, this is correct. Thanks for double-checking.
> Improvements to addDependencyJars
> ---------------------------------
>
> Key: HBASE-9165
> URL: https://issues.apache.org/jira/browse/HBASE-9165
> Project: HBase
> Issue Type: Sub-task
> Components: mapreduce
> Affects Versions: 0.95.2
> Reporter: Nick Dimiduk
> Assignee: Nick Dimiduk
> Fix For: 0.98.0, 0.96.1, 0.94.14
>
> Attachments:
> 0001-HBASE-9165-mapreduce-Modularize-building-dependency-.patch,
> 0001-HBASE-9165-mapreduce-Modularize-building-dependency-.patch,
> 0001-HBASE-9165-mapreduce-Modularize-building-dependency-.patch,
> HBASE-9165-0.94.00.patch
>
>
> The way we support adding HBase dependencies to a MapReduce job in
> {{TableMapReduceUtils#addDependencyJars(job)}} is a bit monolithic. Advanced
> users need a way to add HBase and its dependencies to their job without us
> snooping around for ouput formats and the like (see PIG-3285). We can also
> benefit from a little more code reuse between our {{mapred}} and
> {{mapreduce}} namespaces.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
