hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-13714) Tighten up our compatibility guidelines for Hadoop 3
Date Wed, 03 May 2017 17:11:04 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-13714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15995220#comment-15995220
] 

Allen Wittenauer commented on HADOOP-13714:
-------------------------------------------

bq. Isn't that exactly what we already do

No.  Hadoop has a regular habit of releasing minor versions bumps that regularly break backward
compatibility. Lots of examples: HA-NN breaking single NN upgrade scripts with a NOP rather
than a failure during finalize, audit log output changes, fsck output changes, breaking apart
the hadoop-hdfs jar, NN UI,  ...  Lots to choose from.

However: the vote on bumping the Java version from 6 to 7 will stand out as the moment the
PMC gave clear indication of where compatibility really stands.  That is, by almost all definitions,
the exact moment when one wants to change major version numbers. It went from 0.20 -> 1.0
"version numbers are cheap" to "no way this should be 3.0 because our licensing to our customers
depends upon the ASF release being 2.x".

Again: downstream users treat every minor as a major due to our track record.  Perception
is reality.  They are not wrong.

bq. what this JIRA is attempting to support?

It might, but to quote you:

bq.  The developer community needs to understand what compatibility means and be committed
to upholding it.

They don't care. If there is a conflict between employer's goals and ASF rule set, the employer's
goals wins.  It has happened time and time again in Hadoop.  V2.6.0 and V2.7.0 stand out has
critical releases that really demonstrate this in action. 

> Tighten up our compatibility guidelines for Hadoop 3
> ----------------------------------------------------
>
>                 Key: HADOOP-13714
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13714
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: documentation
>    Affects Versions: 2.7.3
>            Reporter: Karthik Kambatla
>            Assignee: Daniel Templeton
>            Priority: Blocker
>         Attachments: HADOOP-13714.WIP-001.patch
>
>
> Our current compatibility guidelines are incomplete and loose. For many categories, we
do not have a policy. It would be nice to actually define those policies so our users know
what to expect and the developers know what releases to target their changes. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org


Mime
View raw message