You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Sean Busbey (JIRA)" <ji...@apache.org> on 2019/05/31 15:46:00 UTC
[jira] [Reopened] (HBASE-22393) HBOSS: Shaded external dependencies
to avoid conflicts with Hadoop and HBase
[ https://issues.apache.org/jira/browse/HBASE-22393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Busbey reopened HBASE-22393:
---------------------------------
> HBOSS: Shaded external dependencies to avoid conflicts with Hadoop and HBase
> ----------------------------------------------------------------------------
>
> 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
> Labels: HBOSS
> Fix For: hbase-filesystem-1.0.0-alpha1
>
> Attachments: 0001-HBASE-22393-HBOSS-Shade-dependencies-to-prevent-conf.patch, 0001-HBASE-22393.patch, 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)