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

Sean Busbey commented on HBASE-12914:
-------------------------------------

{quote}
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?
{quote}

I only included them because the classes are marked Public. It's really hard to 
know how end users will abuse whatever we have marked as available; even if we 
don't have an obvious direct way for them to be used in normal HBase operations 
it's hard to know that we won't break someone.

{quote}
Should we be marking the protobuf changes as well?
Encryption.proto
HFile.proto trailer field encryption_key
{quote}

The more I think about this, the more I would like us to not mark any protobuf 
stuff unstable (in case anyone was entertaining it).

> 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)

Reply via email to