[
https://issues.apache.org/jira/browse/HBASE-12914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14299749#comment-14299749
]
ramkrishna.s.vasudevan commented on HBASE-12914:
------------------------------------------------
[~busbey]
Thanks for providing the entire list. I thought if the VisibilityExpResolver
is marked Unstable then the CellCreator and ImportTSV related things also
become Unstable because they are used in the ImportTSV tool.
Cell and CellUtil methods related to Tags to be declared UnStable? Currently we
don't allow user to control these tags ie. there are not APIs which allow users
to add a tag in the mutation directly.
Also from the RPC side the tags are filtered out before sending it out to the
clients. So will that make sense to change them to Unstable?
> 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
> Assignee: ramkrishna.s.vasudevan
> Priority: Critical
> Fix For: 0.98.11
>
> Attachments: HBASE-12914-branch-1.patch, HBASE-12914.patch
>
>
> 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)
