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 Thu, 20 Apr 2017 14:30:04 GMT

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

Steve Loughran commented on HADOOP-13714:

pull in [~aw] for his opinions here.

We do have some logs whose output is considered stable: those machine readable ones (HDFS
Audit log &c). I'd like the explicit ones to be listed here with all others considered
open. We can't control the logging or error messages from downstream code either.

Exception class: we can change/they may change under us. Biggest issue here is unchecked exceptions
we sometimes forget to catch and wrap, once wrapped, well, that's a change.
Exception text. I reserve the right to improve/change error messages to be more informative

bq. It would be really nice to support this effort by beefing up the JavaDocs such that they
can serve the role of specifying semantic behaviour.

aah. Potentially the wrong place for this. If you look at the FS Spec, you can see that something
a bit higher level works, ish. What that adds is some model of what the operations are manipulating.
Without that, well, what semantics are you specifying? Vague english-language concepts?

Consider also the tests to be our implicit specification: they are what the implementors/maintainers
expect the implementation to do. Note there, all too often, we have strings containing expectations
about the string values of exception messages.

> 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
> 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