[
https://issues.apache.org/jira/browse/HBASE-12975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14339619#comment-14339619
]
Andrew Purtell commented on HBASE-12975:
----------------------------------------
I'm going to split out the SplitTransaction and RegionMergeTransaction changes
I made in an earlier patch on HBASE-12972 tomorrow and put up a patch here for
master. This should go all the way back to branch-1.0 once we have something
that can be workable though, so Phoenix doesn't have to extend private
externals. Could then work on APIs for registering callbacks for when different
transactions phases happen as mentioned above.
[~busbey]'s point on HBASE-12972 is relevant here too though: If we introduce a
LimitedPrivate interface into a 1.0.x where x > 0, then is it a compatibility
violation since x = 0 wouldn't have the supported/supportable interfaces? I'd
hope not, if perhaps only for this case. Otherwise we cannot extract ourselves
from this unfortunate situation until 1.1.0.
/cc [~enis] [~lhofhansl] [~stack]
> 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)
