[
https://issues.apache.org/jira/browse/HBASE-12975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14358397#comment-14358397
]
Rajeshbabu Chintaguntla commented on HBASE-12975:
-------------------------------------------------
[~apurtell]
bq. As for specifying what region(s) to run a transaction on, can you use the
new factories? Create a factory, call its create() method with the desired
regions(s) to get a transaction instance), and then run it?
This approach is good but confused with the patch. As for the current patch
SplitTransactionImpl supports splitting only one region at a time. If we want
to split multiple regions do we need to have custom implementation? Or just if
we register new transaction listener for other regions? Or still we need to
make the changes in SplitTransactionImpl?
Can you explain bit more how we can add more regions to split transactionally?
Thanks.
> 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)
