[ https://issues.apache.org/jira/browse/HBASE-13103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725094#comment-14725094 ]
Lars George commented on HBASE-13103: ------------------------------------- Nope: {noformat} hbase(main):028:0> alter 'testtable', {NORMALIZATION_ENABLED => 'true'} NameError: uninitialized constant NORMALIZATION_ENABLED {noformat} And even if so, it requires knowledge about the internal key name (says in the Java doc for the key in HTD). > [ergonomics] add region size balancing as a feature of master > ------------------------------------------------------------- > > Key: HBASE-13103 > URL: https://issues.apache.org/jira/browse/HBASE-13103 > Project: HBase > Issue Type: Improvement > Components: Balancer, Usability > Reporter: Nick Dimiduk > Assignee: Mikhail Antonov > Fix For: 2.0.0, 1.2.0, 1.3.0 > > Attachments: HBASE-13103-branch-1.v3.patch, HBASE-13103-v0.patch, > HBASE-13103-v1.patch, HBASE-13103-v2.patch, HBASE-13103-v3.patch > > > Often enough, folks miss-judge split points or otherwise end up with a > suboptimal number of regions. We should have an automated, reliable way to > "reshape" or "balance" a table's region boundaries. This would be for tables > that contain existing data. This might look like: > {noformat} > Admin#reshapeTable(TableName, int numSplits); > {noformat} > or from the shell: > {noformat} > > reshape TABLE, numSplits > {noformat} > Better still would be to have a maintenance process, similar to the existing > Balancer that runs AssignmentManager on an interval, to run the above > "reshape" operation on an interval. That way, the cluster will automatically > self-correct toward a desirable state. -- This message was sent by Atlassian JIRA (v6.3.4#6332)