hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15073) Finer grained control over normalization actions for RegionNormalizer
Date Wed, 06 Jan 2016 03:53:39 GMT

    [ https://issues.apache.org/jira/browse/HBASE-15073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15084950#comment-15084950
] 

Ted Yu commented on HBASE-15073:
--------------------------------

w.r.t. option #1, extra work is placed on user to specify type(s) of actions.
We can interpret that the lack of this second flag means both split and merge are allowed.

Option #2 is not flexible in that the flag doesn't give per table control.

> 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
>            Reporter: Ted Yu
>            Assignee: Ted Yu
>
> 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)

Mime
View raw message