[
https://issues.apache.org/jira/browse/HBASE-6929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13481791#comment-13481791
]
Enis Soztutar commented on HBASE-6929:
--------------------------------------
@Stack
bq. What do we do in hbase 1.0, say, where minimum required is indeed h2. Don't
we want our version to be hbase in that case and not hbase-hadoop2? You think
w/ your patch, maven repo will have hbase-hadoop2 and it will be just fine when
hbase itself moves to hadoop2? (We'll have a hadoop3 version around this time
too?)
If Hbase moves to hadoop2, and drops support for h1, then we can just call the
main version hbase without the hadoop2 suffix. As long as which version of
HBase requires which version of hadoop, it should not be too confusing, wdyt?
@Jarek
bq. Another idea - version number can contain string. So instead of creating
special dot release, what about creating release "${normalversion}-hadoop2"?
This is what I did in the patch. We will release for example
hbase-0.94.3-hadoop2.
> Publish Hbase 0.94 artifacts build against hadoop-2.0
> -----------------------------------------------------
>
> Key: HBASE-6929
> URL: https://issues.apache.org/jira/browse/HBASE-6929
> Project: HBase
> Issue Type: Task
> Components: build
> Affects Versions: 0.94.2
> Reporter: Enis Soztutar
> Attachments: 6929.txt, hbase-6929_v2.patch
>
>
> Downstream projects (flume, hive, pig, etc) depends on hbase, but since the
> hbase binaries build with hadoop-2.0 are not pushed to maven, they cannot
> depend on them. AFAIK, hadoop 1 and 2 are not binary compatible, so we should
> also push hbase jars build with hadoop2.0 profile into maven, possibly with
> version string like 0.94.2-hadoop2.0.
--
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
