[
https://issues.apache.org/jira/browse/HBASE-8258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13624205#comment-13624205
]
Jonathan Hsieh commented on HBASE-8258:
---------------------------------------
[[email protected]] I disagree with stack's comment. I think moving 2.0.3 (a
released version) would be reasonable, but would prefer handling that after we
get this tackled. I'm against 2.0.4-SNAPSHOT (or any *-SNAPSHOT hadoop).
We need be on known good points and ideally move to other known good points.
If it ends up that 2.0.3 breaks us somewhere, I feel that we should stand pat
where we are "stable" until there is a version that works for us or if we are
forced to upgrade. If 2.0.4 (released) is the safe point and it is released,
I'm all for moving to it.
We have enough problems with flaky tests, and I'd rather not have to consider
hadoop code changes shifting under us as another source of bugs. I'm concerned
if upgrading breaks us -- this means hadoop broke compatibility.
> Make mapreduce tests pass on hadoop2
> ------------------------------------
>
> Key: HBASE-8258
> URL: https://issues.apache.org/jira/browse/HBASE-8258
> Project: HBase
> Issue Type: Bug
> Components: mapreduce
> Reporter: stack
> Priority: Blocker
> Fix For: 0.95.1
>
> Attachments: 8258-plain.txt, 8258-v1-hadoop-2.0.txt,
> 8258-v2-hadoop-2.0.txt, 8258-v4-hadoop-2.0.txt, hbase-8258-simple.patch
>
>
> HBASE-7904 was a first attempt at making this work but it got lost in the
> weeds.
> This is a new attempt at making hbase mapreduce jobs run on hadoop2 (w/o
> breaking mapreduce on hadoop1)
--
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
