[
https://issues.apache.org/jira/browse/CRUNCH-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15966407#comment-15966407
]
Jonathan Hsieh commented on CRUNCH-619:
---------------------------------------
What I'm suggesting is that most (if not all) of the code changes should
actually work against hbase 1.x and that the current code is using an api that
is deprecated hbase 1.0. The master branch of crunch is compiling against
hbase 1.0 today. [1]
The hbase 2.0 portions force the issue because the deprecated apis are removed
which forces you to use the hbase 1.0 apis.
I'm confused from your last sentence so let me reword, explictly calling out
projects and versions to make sure we are sure talking about the same thing.
Here's what I think we are suggesting:
1) create new crunch ticket to move to the hbase 1.0.0 api. this should be
testable and committable into crunch. This new ticket could be a blocker for
the next crunch release (crunch 1.0.0?).
2) keep this ticket open and have this deal with the pom changes/transitive
dependency fixes required for working against hbase 2.0.0-alphaX. It will
remain open until a hbase 2.0.0-alpha is available for crunch to build against
and the changes to crunch were made. Whether it is a blocker is up to you
guys.
[1] https://github.com/apache/crunch/blob/master/pom.xml#L104
> Run on HBase 2
> --------------
>
> Key: CRUNCH-619
> URL: https://issues.apache.org/jira/browse/CRUNCH-619
> Project: Crunch
> Issue Type: Improvement
> Affects Versions: 0.14.0
> Reporter: Tom White
> Assignee: Tom White
> Attachments: CRUNCH-619-2.patch, CRUNCH-619.patch, CRUNCH-619_v3.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
