Details
-
Task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
0.90.5, 0.92.0
-
None
-
None
-
Reviewed
-
Adds stability and audience classification annotations on all classes
-
0.96notable
Description
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.
Attachments
Attachments
Issue Links
- is depended upon by
-
HBASE-9495 Sanity check visiblity and audience for hbase-client and hbase-common apis.
- Closed
- relates to
-
HADOOP-5073 Hadoop 1.0 Interface Classification - scope (visibility - public/private) and stability
- Closed