[
https://issues.apache.org/jira/browse/HBASE-9213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740562#comment-13740562
]
Elliott Clark commented on HBASE-9213:
--------------------------------------
Hadoop changed some interfaces in 1.0 to classes in 2.0 (or maybe it was the
other way around I never fully investigated) so the byte code produced isn't
compatible. It should be possible to move all such cases into the shim layer
only, but that work hasn't been done. Because of that I'm not 100% sure that
the hbase-common module is hadoop version agnostic. (That seems like a problem
worth solving)
I believe that the problem of building both compat shims when only one is
needed, has been fixed. If you look at maven now you'll see only one compat
module per build.
> create a unified shim for hadoop 1 and 2 so that there's one build of HBase
> ---------------------------------------------------------------------------
>
> Key: HBASE-9213
> URL: https://issues.apache.org/jira/browse/HBASE-9213
> Project: HBase
> Issue Type: Brainstorming
> Components: build
> Reporter: Sergey Shelukhin
> Fix For: 0.96.0
>
>
> This is a brainstorming JIRA. Working with HBase dependency at this point
> seems to be rather painful from what I hear from other folks. We could do the
> hive model with unified shim, built in such manner that it can work with
> either version, where at build time dependencies for all 2-3 versions are
> pulled and the appropriate one is used for tests, and when running HBase you
> have to point at Hadoop directory to get the dependencies. I am not very
> proficient at maven so not quite certain of the best solution yet.
--
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
