Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 18 Jul 2012 23:22:34 +0000 (UTC)
From: "Lars Hofhansl (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <2049991142.72620.1342653754491.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <724098603.52892.1342274974679.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (HBASE-6396) Fix NoSuchMethodError running
 against hadoop 2.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Lars Hofhansl commented on HBASE-6396:
--------------------------------------

bq. we can move code sections implemented as reflection into version specific implementations guarded by Maven profiles.
Big +1 on this.

bq. I do not think we should "officially" support a Hadoop != 1.0 && 2.0 in our project build and test procedures.
+1 on this too.

bq. I second the idea of adding a hadoop 2.0 profile
Should I file a different jira to add the 2.0 profile to 0.94?

                
> Fix NoSuchMethodError running against hadoop 2.0
> ------------------------------------------------
>
>                 Key: HBASE-6396
>                 URL: https://issues.apache.org/jira/browse/HBASE-6396
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.94.0
>            Reporter: Zhihong Ted Yu
>            Assignee: Zhihong Ted Yu
>              Labels: hadoop-2.0
>             Fix For: 0.96.0
>
>         Attachments: 6396-v2.txt
>
>
> HADOOP-8350 changed the signature of NetUtils.getInputStream()
> This leads to NoSuchMethodError in HBaseClient$Connection.setupIOstreams().
> See https://issues.apache.org/jira/browse/HADOOP-8350?focusedCommentId=13414276&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13414276

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira