[ 
https://issues.apache.org/jira/browse/HADOOP-6677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12853300#action_12853300
 ] 

Tom White commented on HADOOP-6677:
-----------------------------------

+1 However, I wonder if we could go further and not list projects at all. It 
seems odd to mandate a pre-determined audience for a particular API. To me, it 
seems better to say "this is a developer-level interface" (stability is 
independent), which may be used by different projects. A Private API, by 
contrast, is one that may not be used outside the project.

With this simplification, the LimitedPrivate annotation would be interpreted as 
being intended for developers rather than users of Hadoop. This would allow any 
project to use the API, including subprojects, contrib projects, or projects 
that are not a part of Hadoop.

For example, by marking the MapReduce interfaces that schedulers need 
limited-private the scheduler implementations could be hosted anywhere - as 
contrib modules as they are today, or as an independent project - it shouldn't 
matter. Futhermore, by making the Java visibility public, the scheduler 
implementations would not have to be in the same package as the interfaces, as 
they are today. Users would not see these interfaces, since they are not in 
public javadoc.


> InterfaceAudience.LimitedPrivate should take a string not an enum
> -----------------------------------------------------------------
>
>                 Key: HADOOP-6677
>                 URL: https://issues.apache.org/jira/browse/HADOOP-6677
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 0.21.0
>            Reporter: Alan Gates
>            Priority: Minor
>
> Trying to keep the list of all possible components sharing limited private 
> interfaces up to date is painful.  As other subprojects beyond HDFS and MR 
> use this interface it will only get worse (see PIG-1311).  If it is converted 
> to a string other subprojects can use it without requiring patches to common.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to