[
https://issues.apache.org/jira/browse/HBASE-13339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14484483#comment-14484483
]
Nick Dimiduk commented on HBASE-13339:
--------------------------------------
Reviewing comments, I don't see a consensus here for 1.1.
As [~eclark] says, it's silly to ship features that depend on Hadoop 2.6
without actually supporting it in the release. Is it enough to leave the
branch-1.1 poms at hadoop-2.5.x but also run a branch-1.1 jenkins job for
Hadoop 2.6? [~apurtell] had a negative experience maintaining both hadooop-1
and hadoop-2 shims, but the differences between 2.5 and 2.6 should be much
smaller. That way, users who do want access to the new 2.6 features have
confidence that the apache release will run, even if they have to build from
the tag or source tarball themselves.
I guess the other obvious question to ask is: has anyone evaluated how much
change there is between Hadoops 2.5 and 2.6?
> 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
> Attachments: 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)
