hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13339) Update default Hadoop version to 2.6.0
Date Wed, 29 Apr 2015 03:46:07 GMT

    [ https://issues.apache.org/jira/browse/HBASE-13339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14518666#comment-14518666

Sean Busbey commented on HBASE-13339:

Personally, I view the pom as a compile-time API check. However, I get Elliott's concern on
stability for folks who don't listen when we say that they need to replace the jars with their
Hadoop versions. As a part of that, I think we should make sure we push for HDFS-7005 in the
Hadoop 2.5.z line regardless of what we do here.

I don't want to move any versions into "unsupported" in 1.y that were supported at the start
of 1.0, so I'd like to make sure we verify that things still work on e.g. Hadoop 2.4 and 2.5.
I think having Jenkins builds with the appropriate hadoop.profile / hadoop-two.version settings
is enough to fulfill this for me.

Does anyone have a good idea about how we can test what happens when a user of a Hadoop 2.5
cluster upgrades to HBase 1.1 and doesn't replace the Hadoop 2.6 jars we include? (Or similarly
a 2.4 cluster with either the 2.5 jars we're including now or the 2.6 ones?) Since they're
supposed to be wire compatible, I think it should be fine but a test would be better.

I'll check dependency changes, presuming nothing explodes (like a guava version) then I'd
be +0.

-1 on unsupporting 1.1 versions of Hadoop.

[~larsh], are you referring to labeling Hadoop 1.1.z versions as unsupported? If so, they've
always been unsupported on HBase 1.0+ (at least [according to the ref guide|http://hbase.apache.org/book.html#hadoop]).

> 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

View raw message