[ https://issues.apache.org/jira/browse/HBASE-15073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nick Dimiduk resolved HBASE-15073. ---------------------------------- Resolution: Won't Fix Closing old, reverted normalizer issue as "Won't Fix". > 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 > Priority: Major > Attachments: 15073-v1.txt, 15073-v2.txt, 15073-v2.txt, 15073-v3.txt, > 15073-v4.txt, 15073-v5.txt > > > Currently both region split and merge actions are carried out during > normalization for underlying table. > However, for certain use case(s) (see > https://issues.apache.org/jira/browse/HBASE-13103?focusedCommentId=14366255&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14366255), > 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 (v8.3.4#803005)