[
https://issues.apache.org/jira/browse/HBASE-12914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14298193#comment-14298193
]
ramkrishna.s.vasudevan commented on HBASE-12914:
------------------------------------------------
bq.should the interfaces stay IS.Unstable in branch-1 and/or master?
I think this can remain as is in master and branch-1. Because the feature once
released in 1.0 is considered to be stable because V3 is default.
bq.how about the classes involved exclusively in those features?
You mean only the exposed interfaces?
In 0.98 we could mark
VisibilityLabelService, VisibilityExpEvaluator, VisibilityExpressionResolver as
unstable because they are the public facing interfaces. (Any other interface is
missed)?
The other features like ACL does not explicitly expose any API that is bound to
change based on V3. Similar is the case with TTL. So if we mark the interfaces
related to Visibililty as Unstable and add a note in the ref section will it be
fine?
I can take this up [~busbey] if you have not started working on this.
> Mark public features that require HFilev3 Unstable in 0.98, warn in upgrade
> section
> -----------------------------------------------------------------------------------
>
> Key: HBASE-12914
> URL: https://issues.apache.org/jira/browse/HBASE-12914
> Project: HBase
> Issue Type: Bug
> Components: API, documentation
> Affects Versions: 0.98.6, 0.98.7, 0.98.8, 0.98.9
> Reporter: Sean Busbey
> Priority: Critical
> Fix For: 1.0.1, 0.98.11
>
>
> There are several features in 0.98 that require enabling HFilev3 support.
> Some of those features include new extendable components that are marked
> IA.Public.
> Current practice has been to treat these features as experimental. This has
> included pushing non-compatible changes to branch-1 as the API got worked out
> through use in 0.98.
> * Update all of the IA.Public classes involved to make sure they are
> IS.Unstable in 0.98.
> * Update the ref guide section on upgrading from 0.98 -> 1.0 to make folks
> aware of these changes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
