[
https://issues.apache.org/jira/browse/HADOOP-5073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12665103#action_12665103
]
Steve Loughran commented on HADOOP-5073:
----------------------------------------
I am +1 in the different scopes, and in favour of using Java 5 annotations to
mark this up, rather than relying purely on package scoping to hide things. In
the open source world, there's nothing to stop anyone putting their classes in
your package to get at internal stuff, leaving you to field the support calls
with your product name in all the stack traces.
I'd suggest that we have an @Stable marker to all interfaces that are
considered stable; only things that are marked as stable are considered stable,
everything else is inherently unstable/evolving
One thing I would change, the Web GUI is an interface. if you can access it
programmatically -as fsck does- then it has stability issues too.
> 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 Core
> Issue Type: Sub-task
> Reporter: Sanjay Radia
> Assignee: Sanjay Radia
>
> This jira proposes an interface classification for hadoop interfaces.
> The discussion was started in email alias [email protected] in Nov
> 2008.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
