[ https://issues.apache.org/jira/browse/HBASE-12975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14308048#comment-14308048 ]
Lars Hofhansl commented on HBASE-12975: --------------------------------------- So if you had an interface with beforePONR and afterPONR methods, you'd be good? You'd call beforePONR on both transactions and if successful call afterPONR on both? > 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 > Priority: Minor > Fix For: 2.0.0, 1.0.1, 1.1.0, 0.98.11 > > 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)