[
https://issues.apache.org/jira/browse/HBASE-6929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13497416#comment-13497416
]
Hari Shreedharan commented on HBASE-6929:
-----------------------------------------
[[email protected]] If there are no maven artifacts available, then it would
require a user building flume/sqoop against hadoop2 to build hbase against
hadoop2 first - which is not something we really desire. If it is possible to
push the artifacts it would be great. I can update the Flume pom to point to
the hadoop2 version of hbase in the hadoop2 profile - so 0.94.2-hadoop2 would
work fine. Also, could you give an ETA, since Flume-1.3.0 is currently being
voted on, I'd like this to go into the release - so if this does not take too
long, it'd be great, I will ask for another RC.
Thanks!
> 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
