hbase-issues mailing list archives

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

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

Andrew Purtell edited comment on HBASE-12975 at 2/27/15 6:17 PM:
-----------------------------------------------------------------

bq. You mean start HBase 1.+ support for Phoenix 5.0, right?
Just to be precise, the suggestion is to support HBase 1.1 and higher with Phoenix 5.0, but
not HBase 1.0 or lower. Phoenix 4.x would continue to support 0.98. There'd be a gap, nothing
for HBase 1.0.x. We'd work on the timing so HBase 1.1 is released before Phoenix 5.0. 

Alternatively, Phoenix could begin mapping major -dot-minor to HBase starting at 5, so:
- Phoenix 5.0.x -> HBase 1.0.x
- Phoenix 5.1.x -> HBase 1.1.x
- Phoenix 6.x.x -> HBase 2.x.x

For Phoenix 5.0.x you could continue the implementation strategies used for 0.98 since there
wouldn't be alternatives yet. For Phoenix x.y.z where ( x = 5 and y > 0 || x > 5 ) there
would be supportable interfaces for SplitTransaction, RegionMergeTransaction (and a supported
'Region' substitute for HRegion (HBASE-12972))


was (Author: apurtell):
bq. You mean start HBase 1.+ support for Phoenix 5.0, right?
Just to be precise, the suggestion is to support HBase 1.1 and higher with Phoenix 5.0, but
not HBase 1.0 or lower. Phoenix 4.x would continue to support 0.98. There'd be a gap, nothing
for HBase 1.0.x. We'd work on the timing so HBase 1.1 is released before Phoenix 5.0. 

Alternatively, Phoenix could begin mapping major -dot-minor to HBase starting at 5, so:
- Phoenix 5.0.x -> HBase 1.0.x
- Phoenix 5.1.x -> HBase 1.1.x
- Phoenix 6.x.x -> HBase 2.x.x

For Phoenix 5.0.x you could continue the implementation strategies used for 0.98 since there
wouldn't be alternatives yet. For Phoenix x.y.z where x >= 5 and y > 0 there would be
supportable interfaces for SplitTransaction, RegionMergeTransaction (and a supported 'Region'
substitute for HRegion (HBASE-12972))

> 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
(v6.3.4#6332)

Mime
View raw message