You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2014/02/20 02:53:19 UTC

[jira] [Commented] (HBASE-10573) Use Netty 4

    [ https://issues.apache.org/jira/browse/HBASE-10573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13906477#comment-13906477 ] 

Andrew Purtell commented on HBASE-10573:
----------------------------------------

I have brought in Netty 4 and excluded Netty 3 from our Hadoop dependencies. It "works".

It is ugly that hadoop-mapreduce-client-core and hadoop-mapreduce-client-jobclient bring in Netty 3.x as a dependency, possible complications for MR applications using HBase are concerning. So does hadoop-minicluser, but this is completely understandable, so I bring in the old 3.x Netty at test scope, and tests pass.

In terms of HBase code I needed to reimplement the multicast ClusterStatusPublisher (not sure if it works, no test for it) and modify TestFuzzyRowAndColumnRangeFilter.

> Use Netty 4
> -----------
>
>                 Key: HBASE-10573
>                 URL: https://issues.apache.org/jira/browse/HBASE-10573
>             Project: HBase
>          Issue Type: Sub-task
>    Affects Versions: hbase-10191
>            Reporter: Andrew Purtell
>            Assignee: Andrew Purtell
>         Attachments: 10573.patch
>
>
> Pull in Netty 4 and sort out the consequences.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)