[
https://issues.apache.org/jira/browse/HBASE-13339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14514569#comment-14514569
]
Lars Hofhansl commented on HBASE-13339:
---------------------------------------
I think we can commit this one to trunk and then file a separate issue for 1.1+
if we want it there too.
There are a bunch of related issues :)
* If we force a Hadoop upgrade with a minor version of HBase we force folks to
go through the Hadoop upgrade process (need to check whether 2.5->2.6 needs
this).
* If we want to turn 1.1 into 2.0, the current branch-1 becomes effective
branch-2, which means we cannot release the next 1.1 out of that branch.
* If 1.1 is 2.0 instead, which branch do we release 1.1 from? Should be
branched of branch-1.0 then.
My vote would be to
* make this change in master only (which then stays 2.0)
* document how to change it in earlier releases in the HBase book.
[~apurtell], [~stack], [~ndimiduk].
> Update default Hadoop version to 2.6.0
> --------------------------------------
>
> Key: HBASE-13339
> URL: https://issues.apache.org/jira/browse/HBASE-13339
> Project: HBase
> Issue Type: Bug
> Components: build
> Affects Versions: 2.0.0, 1.1.0
> Reporter: Elliott Clark
> Assignee: Elliott Clark
> Priority: Blocker
> Fix For: 2.0.0, 1.1.0, 1.2.0
>
> Attachments: HBASE-13339-v1.patch, HBASE-13339.patch
>
>
> Current default Hadoop version is getting a little long in the tooth. We
> should update to the latest version. The latest version is backwards
> compatible with 2.5.1's dfs and mr so this should be painless.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
