[
https://issues.apache.org/jira/browse/HBASE-22393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16837470#comment-16837470
]
Sean Busbey commented on HBASE-22393:
-------------------------------------
* Why aren't you creating a dependency reduced pom? As is this will include
curator classes but still list curator as a dependency
* Why not shade all dependencies? It'll make it easier to use hboss with a
variety of hbase versions.
* for the shading pattern please use something that won't conflict with either
of the hbase-thirdparty artifacts or the hbase-shaded stuff.
> 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
> Reporter: Sean Mackrory
> Assignee: Sean Mackrory
> Priority: Major
> Attachments: HBASE-22393.001.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)
