[
https://issues.apache.org/jira/browse/HBASE-6396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13417669#comment-13417669
]
Jonathan Hsieh commented on HBASE-6396:
---------------------------------------
@Lars, idealy yeah. Actually, in this case where we have "source-compatible"
changes from hdfs that require recompile, I'd rather not use reflection - we'd
need to run the whole test suite to catch cross-version problems instead of
just doing the compile check that currently happens. (+1 hadoop23 compile check
added to the hadoopqa script).
I created a hadoop 2.0 profile in my local and compiled everything against
hadoop 2.0 jars instead of hadoop 0.23.x jars. This build didn't include this
patch, and seems to have gotten past where the other build got stuck. With
Ted's patch, my guess is that the reflection trick caught one place but that
there are others in the source where the trick needed to be done again.
I second the idea of adding a hadoop 2.0 profile, and possibly dropping hadoop
0.23, 0.21 build support (but keep 0.22 is being used by Ted's crew). Bottom
line, this patch isn't really needed for hadoop 2.0. I'm not sure if this
patch is needed with 0.22 hadoops -- it would be up to folks using that to vet
it there.
> 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
