[
https://issues.apache.org/jira/browse/HADOOP-6668?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864100#action_12864100
]
Sanjay Radia commented on HADOOP-6668:
--------------------------------------
>>I disagree with your metrics example: .... They should be limited private.
>Limited private for use by which components or subprojects?
Limited private to MR and HDFS.
>> How would I write my own metrics context?
Who is "I"? If MR or HDFS developer then he is part of the target audience.
If "I" is an application developer then he runs a risk using a limited-private
API - it may change in incompatible ways of the MR and HDFS projects are okay
with it.
BTW the metrics themselves are also interfaces and they would have their own
classification (but we can't use
the annotations).
> Apply audience and stability annotations to classes in common
> -------------------------------------------------------------
>
> Key: HADOOP-6668
> URL: https://issues.apache.org/jira/browse/HADOOP-6668
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: documentation
> Reporter: Tom White
> Assignee: Tom White
> Priority: Blocker
> Fix For: 0.21.0
>
> Attachments: common.interface-tw-annotated.txt, HADOOP-6668.patch,
> HADOOP-6668.patch, HADOOP-6668.patch, HADOOP-6668.patch, HADOOP-6668.patch,
> HADOOP-6668.patch
>
>
> Mark private implementation classes with the InterfaceAudience.Private or
> InterfaceAudience.LimitedPrivate annotation to exclude them from user Javadoc
> and JDiff.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
