[
https://issues.apache.org/jira/browse/HBASE-4403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13209738#comment-13209738
]
Jimmy Xiang commented on HBASE-4403:
------------------------------------
@Stack, thanks a lot for review. I will incorporate the changes to the next
version.
How about those coprocessor and rest related classes?
As the classification definition, HADOOP-5073 has some info and background.
Todd has a short summary which is very good:
{quote}
if it's Private, we can change it (and dont' need a
stability mark). If it's public but unstable, we can change it. If
it's public/evolving, we're allowed to change it but should try not
to. If it's public and stable we can't change it without a deprecation
path or with a GREAT reason.
{quote}
> 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.90.5, 0.92.0
> Reporter: Todd Lipcon
> Assignee: Jimmy Xiang
> Attachments: hbase-4403-interface.txt,
> hbase-4403-nowhere-near-done.txt
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
