[
https://issues.apache.org/jira/browse/HBASE-12914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14298896#comment-14298896
]
Andrew Purtell commented on HBASE-12914:
----------------------------------------
The *only* reason any of the mentioned interfaces are "unstable", relative to
any other change we have made such as region replicas, API refactorings, load
pushback, etc. etc. is specifically when HFile V3 was introduced out of an
abundance of caution we explicitly said it would be experimental for the
duration of the 0.98 release. The discussion above has gotten way out of hand
in my opinion.
> 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)
