[
https://issues.apache.org/jira/browse/HADOOP-9517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13647160#comment-13647160
]
Steve Loughran commented on HADOOP-9517:
----------------------------------------
think the doc skipped that notion of "semantic compatibility". Even if we make
guarantees that an interface doesn't change, what programs want is both a
stable interface and stable semantics, which we can't guarantee.
The doc implies that anything marked as {{@Stable}} is "required" to be
compatible across versions, meaning no change to the behaviour of an API call
can ever change. Which implies that you can't fix any behaviour that is
considered a defect, and that all unintentional side effects could also be
argued as features.
> Define Hadoop Compatibility
> ---------------------------
>
> Key: HADOOP-9517
> URL: https://issues.apache.org/jira/browse/HADOOP-9517
> Project: Hadoop Common
> Issue Type: Bug
> Components: documentation
> Reporter: Arun C Murthy
> Assignee: Karthik Kambatla
> Attachments: hadoop-9517.patch
>
>
> As we get ready to call hadoop-2 stable we need to better define 'Hadoop
> Compatibility'.
> http://wiki.apache.org/hadoop/Compatibility is a start, let's document
> requirements clearly and completely.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
