[
https://issues.apache.org/jira/browse/HADOOP-13714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152976#comment-16152976
]
Daniel Templeton commented on HADOOP-13714:
-------------------------------------------
I hear ya.
bq. I don't want to encourage things in, say, hadoop-common being marked as
Public just because I want to use them in, say hadoop-hdfs.
If there are Private things in common that are needed from HDFS, then they
should be extended to Limited Private (HDFS). If all of common ends up as
Limited Private (HDFS, MapReduce, YARN), that's fine.
bq. And limited private {mapreduce}, well, we all knows that means "any yarn
app".
Then those thing need to be public. If we have interfaces that are consumed by
the public but that we don't have labeled in a way that enforces compatibility,
that's bad.
> 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
