wchevreuil commented on pull request #1883:
URL: https://github.com/apache/hbase/pull/1883#issuecomment-651722529
> @wchevreuil
> Thought it again, if this new splitPolicy is useable in branch-2.2 and
branch-2.3, but disappear in branch-2.4 without deprecated cycle, is it break
the compatibility guarantee?
Yeah, we can't simply remove it between minor releases.
> IMO, maybe we can do as below:
> 1: In all actived branchs, add this new splitPolicy.
Agreed!
> 2: In minor branch set it as default policy and mark SteppingSpliyPolicy
and IncreasingToUpperBoundRegionSplitPolicy as deprecated, at the same time fix
the ConstantSizeRegionSplitPolicy.
Just to confirm my understanding of your proposal: adding the new policy as
default, deprecation of the overridden ones and fix of
ConstantSizeRegionSplitPolicy should go on master and branch-2 branches, whilst
branch-2.2 and branch-2.3 would only have the new policy added? If so, I'm +1
for that.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
