[
https://issues.apache.org/jira/browse/HADOOP-13714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16154038#comment-16154038
]
Daniel Templeton commented on HADOOP-13714:
-------------------------------------------
Maybe I'm missing your point. Hadoop common is absolutely the common bits for
use by Hadoop, and hence Limited Private (HDFS, MapReduce, YARN, Common) seems
quite reasonable. Is there are reason it isn't?
The point I'm trying to make is that the reason we want to set and uphold rules
around audience and stability is so that we can have a clear and sustainable
contract with the consumers of our interfaces. If we have things that are
labeled Limited Private (MapReduce) that everybody just knows are really
Public, then there's nothing to stop someone who doesn't just know from
breaking those APIs and all the downstream consumers. If we make sure the
Public interfaces are actually labeled as Public, then we can catch the
breakage before it happens.
> 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.001.patch, HADOOP-13714.002.patch,
> HADOOP-13714.003.patch, 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.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
