hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-13714) Tighten up our compatibility guidelines for Hadoop 3
Date Wed, 13 Sep 2017 17:10:00 GMT

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

Steve Loughran commented on HADOOP-13714:

bq.  I would assume a code that is not marked as unstable should be stable.

heh. It's private, so nominally "ours to play with". In reality, things like UGI have long
been public APIs, so caution is needed changing even those things. If was mandatory to mark
unstable code as @Unstable, then all which would happen is a very large patch would mark everything
as uch.

h3. protocol vs code

we can set things up so that  Hadoop 2.8.0 JARs & the 2.8.2 JARs are internally consistent
even if you cant mix hadoop-common 2.8.0 and hadoo-hdfs-2.8.2. What we can't do is expect
everyone to upgrade to Hadoop 2.8.2 everywhere simultaneously. Hence: protocols considered
more sensitive to change

Audit logs
bq.  Let’s say a certain event was not logged before but it should be.

The goal here is that the format remains parseable, even if a new event is added. Maybe that
should be explicit. Example: HDFS audit log.

bq. Regarding this let’s call out C compiler and and runtime requirements.


> 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: Compatibility.pdf, HADOOP-13714.001.patch, HADOOP-13714.002.patch,
HADOOP-13714.003.patch, HADOOP-13714.004.patch, HADOOP-13714.WIP-001.patch, InterfaceClassification.pdf
> 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

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

View raw message