[
https://issues.apache.org/jira/browse/HBASE-12975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14384320#comment-14384320
]
Andrew Purtell commented on HBASE-12975:
----------------------------------------
{quote}
And also as stack mentioned here
https://issues.apache.org/jira/browse/HBASE-12975?focusedCommentId=14367729&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14367729
Instead of using SplitTransactionImpl directly It's better to use split
transaction implementation created from factory based on configuration.
{quote}
The latest patch does this, except for in some unit tests. But I will double
check that some hunk wasn't missed.
> 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, 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)
