Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C28D3D3EB for ; Mon, 12 Nov 2012 13:45:14 +0000 (UTC) Received: (qmail 5175 invoked by uid 500); 12 Nov 2012 13:45:14 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 4900 invoked by uid 500); 12 Nov 2012 13:45:13 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 4793 invoked by uid 99); 12 Nov 2012 13:45:12 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Nov 2012 13:45:12 +0000 Date: Mon, 12 Nov 2012 13:45:12 +0000 (UTC) From: "nkeywal (JIRA)" To: issues@hbase.apache.org Message-ID: <1496230323.100369.1352727912397.JavaMail.jiratomcat@arcas> In-Reply-To: <457281521.74052.1352201653498.JavaMail.jiratomcat@arcas> Subject: [jira] [Commented] (HBASE-7104) HBase includes multiple versions of netty: 3.5.0; 3.2.4; 3.2.2 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-7104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495259#comment-13495259 ] nkeywal commented on HBASE-7104: -------------------------------- Committed to trunk. I had multiple errors when I tested before commit, but not on the same tests. So... For 2.0.2 alpha, I would expect that it can be changed on the hadoop side? After all, the netty 3.5 is now at subversion 3.5.9, so could be considered as reliable now... > HBase includes multiple versions of netty: 3.5.0; 3.2.4; 3.2.2 > -------------------------------------------------------------- > > Key: HBASE-7104 > URL: https://issues.apache.org/jira/browse/HBASE-7104 > Project: HBase > Issue Type: Bug > Components: build > Affects Versions: 0.96.0 > Reporter: nkeywal > Assignee: nkeywal > Priority: Minor > Fix For: 0.96.0 > > Attachments: 7104.v1.patch > > > We've got 3 of them on trunk. > [INFO] org.apache.hbase:hbase-server:jar:0.95-SNAPSHOT > [INFO] +- io.netty:netty:jar:3.5.0.Final:compile > [INFO] +- org.apache.zookeeper:zookeeper:jar:3.4.3:compile > [INFO] | \- org.jboss.netty:netty:jar:3.2.2.Final:compile > [INFO] org.apache.hbase:hbase-hadoop2-compat:jar:0.95-SNAPSHOT > [INFO] +- org.apache.hadoop:hadoop-client:jar:2.0.2-alpha:compile > [INFO] | +- org.apache.hadoop:hadoop-mapreduce-client-app:jar:2.0.2-alpha:compile > [INFO] | | \- org.jboss.netty:netty:jar:3.2.4.Final:compile > The patch attached: > - fixes this for hadoop 1 profile > - bump the netty version to 3.5.9 > - does not fix it for hadoop 2. I don't know why, but I haven't investigate: as it's still alpha may be they will change the version on hadoop side anyway. > Tests are ok. > I haven't really investigated the differences between netty 3.2 and 3.5. A quick search seems to say it's ok, but don't hesitate to raise a warning... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira