[
https://issues.apache.org/jira/browse/HBASE-6929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13497468#comment-13497468
]
Roman Shaposhnik commented on HBASE-6929:
-----------------------------------------
A couple of points
# I was saying that if HBase project would not want to get into the business
of certifying that HBase is known to work against Hadoop 2 it can safely NOT
publish the artifacts and expect downstream projects to build local copies of
HBase
# Bigtop 0.4.0 and 0.5.0 do fair amount of testing of the HBase 0.94.X and
Hadoop 2.0.X combination
# If you keep #1 and #2 in mind -- you might be interested in outsourcing the
management of the hadoop2 HBase artifact to the Bigtop project. If that is an
attractive option -- lets talk.
> 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
