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] [Commented] (HBASE-12975) Supportable SplitTransaction and RegionMergeTransaction interfaces
Date Tue, 17 Mar 2015 17:03:39 GMT

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

Andrew Purtell commented on HBASE-12975:
----------------------------------------

Thanks for the pointer [~jamestaylor], I had not seen that issue yet.

So [~rajeshbabu], it looks ok to proceed with this patch as-is. We could even drop the listener
interface, but I suppose that could be independently useful, even though there would be no
user for it today. Should we need to group more than one SplitTransaction into an uber-transaction,
we can enhance the API with something like the "SplitTransactions" suggestion I made above.

Unless I hear otherwise I will refresh the current patch and get it ready for review for commit.

> Supportable SplitTransaction and RegionMergeTransaction interfaces
> ------------------------------------------------------------------
>
>                 Key: HBASE-12975
>                 URL: https://issues.apache.org/jira/browse/HBASE-12975
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Rajeshbabu Chintaguntla
>            Assignee: Andrew Purtell
>             Fix For: 2.0.0, 1.1.0
>
>         Attachments: HBASE-12975.patch, 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