You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "nkeywal (JIRA)" <ji...@apache.org> on 2012/11/06 12:40:12 UTC

[jira] [Updated] (HBASE-7104) HBase includes multiple versions of netty: 3.5.0; 3.2.4; 3.2.2

     [ https://issues.apache.org/jira/browse/HBASE-7104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

nkeywal updated HBASE-7104:
---------------------------

    Status: Patch Available  (was: Open)
    
> 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