[
https://issues.apache.org/jira/browse/HBASE-13604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14544576#comment-14544576
]
Nick Dimiduk commented on HBASE-13604:
--------------------------------------
I committed this to branch-1.0, but maybe changing the dependency resolution
semantics is not valid for a patch release. Thoughts [~enis] [~busbey]. I'm
concerned this may break clients that don't otherwise depend on Yammer Metrics
now needing it in their classpath at runtime (ie, phoenix uberjars).
cc [[email protected]], [~jamestaylor], [~gabriel.reid]
> bin/hbase mapredcp does not include yammer-metrics jar
> ------------------------------------------------------
>
> Key: HBASE-13604
> URL: https://issues.apache.org/jira/browse/HBASE-13604
> Project: HBase
> Issue Type: Bug
> Reporter: Nick Dimiduk
> Assignee: Nick Dimiduk
> Priority: Minor
> Fix For: 2.0.0, 0.98.13, 1.0.2, 1.2.0, 1.1.1
>
> Attachments: HBASE-13604.00-0.98.patch, HBASE-13604.00.patch
>
>
> Noticed this while testing hive integration with HBase snapshots. The yammer
> metrics jar is needed for working with snapshots, but we don't include it in
> the {{bin/hbase mapredcp}} output. That means the necessary classes are not
> on Hive's classpath by default.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
