[
https://issues.apache.org/jira/browse/HBASE-4403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13104342#comment-13104342
]
Todd Lipcon commented on HBASE-4403:
------------------------------------
The impetus to do this now is that, with coprocessors, we may have more people
integrating against APIs that were previously only used internal to the RS. For
example, we may need to be more careful about preserving the HRegion API in
future versions, since coprocessors may use it directly. We don't need to mark
it stable yet, but we should start making more explicit decisions about when we
break interfaces, etc.
This will also help clean up our JavaDoc to avoid mixing all the internal APIs
with things the users are expected to care about.
> Adopt interface stability/audience classifications from Hadoop
> --------------------------------------------------------------
>
> Key: HBASE-4403
> URL: https://issues.apache.org/jira/browse/HBASE-4403
> Project: HBase
> Issue Type: Task
> Affects Versions: 0.92.0, 0.90.5
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
>
> As HBase gets more widely used, we need to be more explicit about which APIs
> are stable and not expected to break between versions, which APIs are still
> evolving, etc. We also have many public classes that are really internal to
> the RS or Master and not meant to be used by users. Hadoop has adopted a
> classification scheme for audience (public, private, or limited-private) as
> well as stability (stable, evolving, unstable). I think we should copy these
> annotations to HBase and start to classify our public classes.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
