hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-12975) SplitTranaction, RegionMergeTransaction to should have InterfaceAudience of LimitedPrivate(Coproc,Phoenix)
Date Fri, 27 Feb 2015 18:35:04 GMT

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

James Taylor commented on HBASE-12975:

Another alternative would be to have an HBase 1.0 compliant Phoenix release still with 4.x
version (i.e. we'd likely need a separate branch, but it wouldn't necessarily need to be a
major release from the Phoenix POV). [~jeffreyz] assures me that we can meet our b/w compat
contract (i.e. mix of Phoenix 4.x clients would be ok against Phoenix 4.x server on HBase
1.0 with PHOENIX-1642).The reason not to go with a major release for Phoenix is because it'd
be good to reserve this for changes that cannot be made b/w compatible.

Maybe move this Phoenix-specific version discussion over to the Phoenix mailing list?

> SplitTranaction, RegionMergeTransaction to should have InterfaceAudience of LimitedPrivate(Coproc,Phoenix)
> ----------------------------------------------------------------------------------------------------------
>                 Key: HBASE-12975
>                 URL: https://issues.apache.org/jira/browse/HBASE-12975
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Rajeshbabu Chintaguntla
>            Assignee: Rajeshbabu Chintaguntla
>             Fix For: 2.0.0, 1.0.1, 1.1.0
>         Attachments: HBASE-12975.patch
> Making SplitTransaction, RegionMergeTransaction limited private is required to support
local indexing feature in Phoenix to ensure regions colocation. 
> We can ensure region split, regions merge in the coprocessors in few method calls without
touching internals like creating zk's, file layout changes or assignments.
> 1) stepsBeforePONR, stepsAfterPONR we can ensure split.
> 2) meta entries can pass through coprocessors to atomically update with the normal split/merge.
> 3) rollback on failure.

This message was sent by Atlassian JIRA

View raw message