[ https://issues.apache.org/jira/browse/HBASE-15073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086239#comment-15086239 ]
Mikhail Antonov commented on HBASE-15073: ----------------------------------------- I think user who may access this API is already supposed to be advanced enough to know about split / merge normalization (provided there's javadoc for that). I don't think we should have 2 method for essentially the same thing, one for "less" advanced, one for "more" advanced user? > Finer grained control over normalization actions for RegionNormalizer > --------------------------------------------------------------------- > > Key: HBASE-15073 > URL: https://issues.apache.org/jira/browse/HBASE-15073 > Project: HBase > Issue Type: Task > Components: regionserver > Reporter: Ted Yu > Assignee: Ted Yu > Fix For: 2.0.0, 1.2.0, 1.3.0 > > Attachments: 15073-v1.txt, 15073-v2.txt, 15073-v2.txt, 15073-v3.txt, > 15073-v4.txt > > > Currently both region split and merge actions are carried out during > normalization for underlying table. > However, for certain use case(s), it would be desirable to perform only one > type of action. > There is one boolean flag, keyed by NORMALIZATION_ENABLED_KEY, per table that > enables normalization. > To provide finer grained control, we have several options: > 1. introduce another per table flag to indicate which type(s) of actions are > allowed ("N" for disabled, "S" for split only, "M" for merge only and "MS" > for both split and merge) > 2. introduce another global flag to indicate which type(s) of actions are > allowed > 3. modify the meaning of existing flag keyed by NORMALIZATION_ENABLED_KEY so > that it indicates type(s) of actions -- This message was sent by Atlassian JIRA (v6.3.4#6332)