[
https://issues.apache.org/jira/browse/HBASE-9213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13740539#comment-13740539
]
Sergey Shelukhin commented on HBASE-9213:
-----------------------------------------
I wonder what the advantage of this model is though. You have two separate
builds for what is essentially the same code, as opposed to one that can be
used with both versions of Hadoop.
Will hbase-common-hadoop1 work with hadoop2 if you upgrade to hadoop2 and
replace the dependencies in hbase classpath? If yes this is still confusing,
and an unnecessary coupling.
PS: there's also
https://repository.apache.org/content/groups/snapshots/org/apache/hbase/hbase-hadoop1-compat/0.95.2-hadoop2-SNAPSHOT/
> 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
