[
https://issues.apache.org/jira/browse/HADOOP-13714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16115019#comment-16115019
]
Daniel Templeton commented on HADOOP-13714:
-------------------------------------------
[~chris.douglas], will do.
[~steve_l], re: {quote}no this is silly. The whole of hadoop-common is full of
private code, yarn co intermixed, things using HDFS config constants where
there is no public one, etc. The whole meaning "Private" is "internal use
within the same hadoop release", at least to me.{quote} If there are places
where private interfaces aren't being respected, we should consider making them
limited private. We obviously can't just flip a switch and make everything
compliant to a new compat spec overnight, but we can draw some lines in the
sand and start trying to make things better.
> 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.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: [email protected]
For additional commands, e-mail: [email protected]
