[
https://issues.apache.org/jira/browse/HADOOP-5073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakob Homan updated HADOOP-5073:
--------------------------------
Attachment: COMMON-5073.patch
Implemented the current state of agreement, incorporating some of Nicholas'
comments.
The current form ends up looking something like this:
{code}
@Audience.LimitedPrivate({Project.HDFS, Project.AVRO})
@ApiStability(Stability.Evolving)
public abstract class Foo extends Configured implements Closeable {
{code}
The ApiStability annotation seems to have flown under the radar in terms of
debates of naming, etc. Using the Project enum puts us back to having to a
rather bulky syntax, but at this point, I'd just as assume have people do
static imports if they really want it to look clean.
For initial project inclusion, all of the nine Hadoop subprojects are included,
per an offline discussion with Owen. The annotations have been placed in a new
package, Classification.
> 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,
> COMMON-5073.patch, 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.
