[
https://issues.apache.org/jira/browse/HBASE-12914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14298830#comment-14298830
]
Sean Busbey commented on HBASE-12914:
-------------------------------------
Few more:
* org.apache.hadoop.hbase.security.visibility.* (i.e. Authorizations,
CellVisibility, VisibilityClient, etc)
* org.apache.hadoop.hbase.mapreduce.CellCreator VISIBILITY_EXP_RESOLVER_CLASS
* org.apache.hadoop.hbase.mapreduce.CellCreator the methods that takes a vis
expressions and getVisibilityExpressionResolver
* org.apache.hadoop.hbase.mapreduce.ImportTsv CELL_VISIBILITY_COLUMN_SPEC,
CELL_TTL_COLUMN_SPEC, DEFAULT_CELL_VISIBILITY_COLUMN_INDEX,
DEFAULT_CELL_TTL_COLUMN_INDEX
* org.apache.hadoop.hbase.mapreduce.ImportTsv all of the public methods related
to per-cell ttl or visibility
* org.apache.hadoop.hbase.mapreduce.TsvImporterMapper members
cellVisibilityExpr and ttl
on branch-1 (but not an issue on 0.98)
* We should annotate the per-cell methods that are unstable in sub-classes of
Mutation as well, to remove ambiguity.
* For the same reason, Scan needs the same things annotated as Query
I'm not clear on if we're considering APIs related to Cell Tags themselves
unstable. If so
* HColumnDescriptor methods about how tags should be handled
* Cell methods related to tags
* CellUtil methods related to tags
* org.apache.hadoop.hbase.mapreduce.CellCreator any of the methods that use Tag
> 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)
