[
https://issues.apache.org/jira/browse/HBASE-13339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14520999#comment-14520999
]
Andrew Purtell commented on HBASE-13339:
----------------------------------------
I missed all the fun while out sick. Appreciate the clarifications from
[~cnauroth] . I think as long as a Hadoop version bump can be handed in
production as a rolling upgrade, then operationally its no worse then our
story, so doesn't constitute a major change in that respect. Rolling downgrade
not being there yet is kind of scary though.
Should we also ensure that users can still build HBase using the earliest
Hadoop version specified as dependency on the HBase release line? eg a user can
build any 1.x with -Dhadoop-two.version set to what shipped with 1.0?
> 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.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)
