[
https://issues.apache.org/jira/browse/HADOOP-10506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13971806#comment-13971806
]
Haohui Mai commented on HADOOP-10506:
-------------------------------------
bq. The reason I ran into this was because I am writing an application to run
on yarn and also another one to just read HDFS files. Its almost impossible (if
not impossible) to do that properly (with security) without using classes
marked LimitedPrivate right now. If it is possible it would require copying
lots of code. We should be making writing applications as easy as possible.
Can you elaborate on this and create jiras? Let's fix them in HDFS.
> LimitedPrivate annotation not useful
> ------------------------------------
>
> Key: HADOOP-10506
> URL: https://issues.apache.org/jira/browse/HADOOP-10506
> Project: Hadoop Common
> Issue Type: Bug
> Affects Versions: 3.0.0, 2.4.0
> Reporter: Thomas Graves
>
> The LimitedPrivate annotation isn't useful. The intention seems to have been
> those interfaces were only intended to be used by these components. But in
> many cases those components are separate from core hadoop. This means any
> changes to them will break backwards compatibility with those, which breaks
> the new compatibility rules in Hadoop.
> Note that many of the annotation are also not marked properly, or have fallen
> out of date. I see Public Interfaces that use LimitedPrivate classes in the
> api. (TokenCache using Credentials is an example).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
