Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 3053F200B40 for ; Thu, 16 Jun 2016 22:54:07 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 2EFC41602C5; Thu, 16 Jun 2016 20:54:07 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 75AE3160A51 for ; Thu, 16 Jun 2016 22:54:06 +0200 (CEST) Received: (qmail 45131 invoked by uid 500); 16 Jun 2016 20:54:05 -0000 Mailing-List: contact issues-help@drill.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@drill.apache.org Delivered-To: mailing list issues@drill.apache.org Received: (qmail 45104 invoked by uid 99); 16 Jun 2016 20:54:05 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Jun 2016 20:54:05 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 3CD9B2C1F62 for ; Thu, 16 Jun 2016 20:54:05 +0000 (UTC) Date: Thu, 16 Jun 2016 20:54:05 +0000 (UTC) From: "Aditya Kishore (JIRA)" To: issues@drill.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (DRILL-4727) Exclude netty from HBase Client's transitive dependencies MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 16 Jun 2016 20:54:07 -0000 [ https://issues.apache.org/jira/browse/DRILL-4727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15334658#comment-15334658 ] Aditya Kishore commented on DRILL-4727: --------------------------------------- The problem is that Drill uses {{netty}} in its various bits and pieces {{(netty-buffer, netty-codec, netty-common, etc...)}} instead of using the uber netty library, i.e. {{netty-all}}. So if a class, {{io.netty.channel.ChannelOption}} in this case, is loaded from one version of one of the bits (netty-transport) while a dependent class (io.netty.util.UniqueName) from the uber jar, conflicts like this can happen. The right fix would be to move Drill to use the uber jar so that its version can override any other components'. For now, since we are so close to release 1.7 release, I'd like to just exclude the {{netty-all}} jar from {{hbase-client}}'s list of dependencies. > Exclude netty from HBase Client's transitive dependencies > --------------------------------------------------------- > > Key: DRILL-4727 > URL: https://issues.apache.org/jira/browse/DRILL-4727 > Project: Apache Drill > Issue Type: Bug > Components: Tools, Build & Test > Affects Versions: 1.7.0 > Reporter: Aditya Kishore > Assignee: Aditya Kishore > Priority: Critical > > Reported on dev/user list after moving to HBase 1.1 > {noformat} > Hi Aditya, > I tested the latest version and got this exception and the drillbit fail to startup . > Exception in thread "main" java.lang.NoSuchMethodError: io.netty.util.UniqueName.(Ljava/lang/String;)V > at io.netty.channel.ChannelOption.(ChannelOption.java:136) > at io.netty.channel.ChannelOption.valueOf(ChannelOption.java:99) > at io.netty.channel.ChannelOption.(ChannelOption.java:42) > at org.apache.drill.exec.rpc.BasicServer.(BasicServer.java:63) > at org.apache.drill.exec.rpc.user.UserServer.(UserServer.java:74) > at org.apache.drill.exec.service.ServiceEngine.(ServiceEngine.java:78) > at org.apache.drill.exec.server.Drillbit.(Drillbit.java:108) > at org.apache.drill.exec.server.Drillbit.start(Drillbit.java:285) > at org.apache.drill.exec.server.Drillbit.start(Drillbit.java:271) > at org.apache.drill.exec.server.Drillbit.main(Drillbit.java:267) > It will working if I remove jars/3rdparty/netty-all-4.0.23.Final.jar, the drill can startup. I think there have some package dependency version issue, do you think so ? > {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)