[
https://issues.apache.org/jira/browse/HBASE-13339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14382332#comment-14382332
]
Sean Busbey commented on HBASE-13339:
-------------------------------------
{quote}
I still think the point stands. If we are shipping a feature that requires a
version of hadoop then we're pulling that version in; be it by doing it
ourselves, or by asking users to do it. So if we have two different versions of
hadoop that we're bound to ( one that we shipped in 1.0.0 and one that features
depend on) then I would rather ship the better newer version by default.
{quote}
It's the difference between letting downstream users decide if the feature is
worth the pain of upgrading or making part of the decision for them. Granted,
folks are supposed to replace the Hadoop related client jars from our lib
directory to be those from their Hadoop distribution. However, giving clear
instructions on replacing Hadoop's transitive dependencies is difficult (and I
don't think we even try right now).
Additionally, it's dangerous to use a backwards-compatible (but not forward
compatible) newer version when we claim support for the older version. It's
doable given test infra, but right now we have a gap on that. Pre-commit QA
keeps us honest on compile and the part of the runtime covered by unit tests,
but we have a clear gap on coverage.
> 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)
