[
https://issues.apache.org/jira/browse/HBASE-22393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16837556#comment-16837556
]
Sean Mackrory commented on HBASE-22393:
---------------------------------------
{quote}Why aren't you creating a dependency reduced pom?{quote}
That's ... a very good question. Now shading all the dependencies except for
things in test & provided scope with the prefix you suggested. Instead of
re-shading all of hbase-thirdparty, the only thing I'm using is Guava's
VisibleForTesting so I just shade that directly and dropped the old dependency.
> HBOSS: Shade curator to prevent conflict with Hadoop
> ----------------------------------------------------
>
> Key: HBASE-22393
> URL: https://issues.apache.org/jira/browse/HBASE-22393
> Project: HBase
> Issue Type: Bug
> Components: Filesystem Integration
> Affects Versions: hbase-filesystem-1.0.0-alpha1
> Reporter: Sean Mackrory
> Assignee: Sean Mackrory
> Priority: Critical
> Fix For: hbase-filesystem-1.0.0-alpha1
>
> Attachments: HBASE-22393.001.patch, HBASE-22393.002.patch
>
>
> Hadoop uses a very old version of Curator, and if it ever ends up in the
> classpath with HBOSS you can get this:
> {code}Exception in thread "main" java.lang.IllegalAccessError: tried to
> access method
> org.apache.curator.framework.recipes.locks.InterProcessMutex.isOwnedByCurrentThread()Z
> from class org.apache.hadoop.hbase.oss.sync.ZKTreeLockManager{code}
> I think the simplest solution is to just shade Curator.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
