hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12914) Mark public features that require HFilev3 Unstable in 0.98, warn in upgrade section
Date Fri, 30 Jan 2015 05:05:34 GMT

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

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

I have not started at all. It would be great if you could take this up.

Please note that we can push the change from Evolving -> Unstable in branch-1, but we can't
push it to branch-1.0 unless the current RC fails.

bq. The other features like ACL does not explicitly expose any API that is bound to change
based on V3. Similar is the case with TTL. So if we mark the interfaces related to Visibililty
as Unstable and add a note in the ref section will it be fine?

I don't think that's quite enough. For example, per-cell TTL means that Mutation.setTTL and
Mutation.getTTL should be marked 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
>            Priority: Critical
>             Fix For: 1.0.1, 0.98.11
>
>
> 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)

Mime
View raw message