[
https://issues.apache.org/jira/browse/HADOOP-12913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15189332#comment-15189332
]
Jason Lowe commented on HADOOP-12913:
-------------------------------------
+1, sounds good to me. IMHO LimitedPrivate has little utility given we now
support rolling upgrades. Changing anything marked LimitedPrivate in a
backwards-incompatible way usually has the same ramifications of doing the same
to something marked Public, because normally nobody is willing to break the
listed downstream projects upgrading their cluster. And like this case, it's
often difficult or impossible to develop "real" applications without using a
lot of the things marked LimitedPrivate which is why those downstream projects
use them.
> Drop the @LimitedPrivate maker off UGI, as its clearly untrue
> -------------------------------------------------------------
>
> Key: HADOOP-12913
> URL: https://issues.apache.org/jira/browse/HADOOP-12913
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: security
> Affects Versions: 2.8.0
> Reporter: Steve Loughran
>
> UGI declares itself as
> {code}
> {@InterfaceAudience.LimitedPrivate({"HDFS", "MapReduce", "HBase", "Hive",
> "Oozie"})
> {code}
> Really its "any application that interacts with services in a secure
> cluster".
> I propose: replace with {{@Public, @Evolving}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
