[
https://issues.apache.org/jira/browse/HBASE-18943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16244517#comment-16244517
]
Josh Elser commented on HBASE-18943:
------------------------------------
bq. Ideally we would be using hadoop-client, not hadoop-common, right? But we
can't because we have some hacks around their internals, AFAICT.
I believe both hadoop-hdfs-client and hadoop-client are bringing in
hadoop-common which will hose us.
Maybe there's something else entirely we should be using (didn't Sean do some
work in Hadoop on shading too)? Configuration is still defined in
hadoop-common; that's one concrete thing would require us to keep using
hadoop-common (or at least the classes contained within).
> Cannot start mini dfs cluster using hadoop-3 in test due to NoSuchMethodError
> in jetty
> ---------------------------------------------------------------------------------------
>
> Key: HBASE-18943
> URL: https://issues.apache.org/jira/browse/HBASE-18943
> Project: HBase
> Issue Type: Bug
> Reporter: Ted Yu
> Priority: Blocker
> Fix For: 2.0.0-beta-1
>
>
> When starting mini dfs cluster against hadoop-3:
> {code}
> dfsCluster = startMiniDFSCluster(numDataNodes, dataNodeHosts);
> {code}
> The above call would end up with:
> {code}
> java.lang.NoSuchMethodError:
> org.eclipse.jetty.server.session.SessionHandler.getSessionManager()Lorg/eclipse/jetty/server/SessionManager;
> at org.apache.hadoop.hbase.client.TestHCM.setUpBeforeClass(TestHCM.java:251)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)