You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (Commented) (JIRA)" <ji...@apache.org> on 2012/03/01 19:01:58 UTC

[jira] [Commented] (HBASE-4403) Adopt interface stability/audience classifications from Hadoop

    [ https://issues.apache.org/jira/browse/HBASE-4403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13220192#comment-13220192 ] 

stack commented on HBASE-4403:
------------------------------

For those following behind, this patch went in in two batches.  First the doc change and then the bulk went in mistakenly as a commit against hbase-5502.  I left the commit but then edited the commit message to say the below:

{code}
Author: stack
Revision: 1295710
Modified property: svn:log

Modified: svn:log at Thu Mar  1 17:57:34 2012
------------------------------------------------------------------------------
--- svn:log (original)
+++ svn:log Thu Mar  1 17:57:34 2012
@@ -1 +1 @@
-HBASE-5502 region_mover.rb fails to load regions back to original server for regions only containing empty tables.
+HBASE-4403 Adopt interface stability/audience classifications from Hadoop AND HBASE-5502 region_mover.rb fails to load regions back to original server for regions only containing empty tables
{code}

                
> 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
>             Fix For: 0.96.0
>
>         Attachments: hbase-4403-interface.txt, hbase-4403-interface_v2.txt, hbase-4403-interface_v3.txt, hbase-4403-nowhere-near-done.txt, hbase-4403.patch, hbase-4403.patch
>
>
> 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