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

Tsz Wo (Nicholas), SZE commented on HADOOP-5073:
------------------------------------------------

There is a problem of using multiple classes (either nested or non-nested 
classes).  It allows multiple annotations for a single entry, e.g.
{code}
@Audience.Public
@Audience.Private
public class HelloWorld {
}
{code}
It is even worst if the annotation is @Inherited because there is no way to 
remove the inherited annotations in the sub-classes.  e.g.
{code}
@Audience.Public
public class Base {
}

@Audience.Private
public class Sub extends Base {
}
{code}
Sub indeed is annotated with both @Audience.Public and @Audience.Private if the 
annotations are @Inherited and there is no way to remove @Audience.Public from 
Sub.

> Hadoop 1.0 Interface Classification - scope (visibility - public/private) and 
> stability
> ---------------------------------------------------------------------------------------
>
>                 Key: HADOOP-5073
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5073
>             Project: Hadoop Common
>          Issue Type: Sub-task
>            Reporter: Sanjay Radia
>            Assignee: Sanjay Radia
>         Attachments: 5073_demo.png, c5073_20090825.patch, c5073_20090825.png, 
> HADOOP-5073.patch, Nested.png, Picture 1.png
>
>
> This jira proposes an interface classification for hadoop interfaces.
> The discussion was started in email alias core-...@hadoop.apache.org in Nov 
> 2008.

-- 
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