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

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

I presume anything in the shell is covered under our "Operational 
Compatibility" section? That would mean we don't need to mark any of it, since 
it has the same limitations as Public Unstable.

This is getting big enough that a reviewboard would help (atleast for me).

* please do documentation updates on master branch; we use that to generate 
documentation for all versions.

Things that also need to be marked Unstable:
* HColumnDescriptor ENCRYPTION and ENCRYPTION_KEY
* HConstants CRYPTO_*
* org.apache.hadoop.hbase.io.crypto.*
* org.apache.hadoop.hbase.util.EncryptionTest

Should we be marking the protobuf changes as well?

* Encryption.proto
* HFile.proto trailer field encryption_key


> 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: 1.0.1, 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