You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Sergey Shelukhin (JIRA)" <ji...@apache.org> on 2013/03/27 19:37:18 UTC
[jira] [Commented] (HBASE-7875) introduce a compaction switch in
HBase Shell
[ https://issues.apache.org/jira/browse/HBASE-7875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13615611#comment-13615611 ]
Sergey Shelukhin commented on HBASE-7875:
-----------------------------------------
+0 on feature - if it makes sense as global config setting it could be added as a config setting and it should work for both table and column family implicitly (will have to be asked of the store, not region, though).
+1 on patch
> introduce a compaction switch in HBase Shell
> --------------------------------------------
>
> Key: HBASE-7875
> URL: https://issues.apache.org/jira/browse/HBASE-7875
> Project: HBase
> Issue Type: New Feature
> Components: shell
> Affects Versions: 0.96.0
> Reporter: Liang Xie
> Assignee: Liang Xie
> Priority: Trivial
> Attachments: HBASE-7875.txt
>
>
> A trivial patch to add an per-table compaction switch. it would be helpful for OPS or manual testing in real cluster, etc.
> Usage:
> hbase(main):016:0> alter 'YCSBTest', {METHOD => 'table_att', COMPACTION_ENABLE => 'FALSE'}
> Updating all regions with the new schema...
> 64/64 regions updated.
> Done.
> 0 row(s) in 1.1290 seconds
> hbase(main):017:0> describe 'YCSBTest'
> DESCRIPTION ENABLED
> {NAME => 'YCSBTest', COMPACTION_ENABLE => 'false', SPLIT_POLICY => 'org.apache.hadoop.hbase.regionserver.ConstantSizeRegionSplitPoli true
> cy', FAMILIES => [{NAME => 'test', DATA_BLOCK_ENCODING => 'NONE', BLOOMFILTER => 'NONE', REPLICATION_SCOPE => '0', COMPRESSION => 'S
> NAPPY', VERSIONS => '1', TTL => '2147483647', MIN_VERSIONS => '0', KEEP_DELETED_CELLS => 'false', BLOCKSIZE => '65536', ENCODE_ON_DI
> SK => 'true', IN_MEMORY => 'false', BLOCKCACHE => 'true'}]}
> 1 row(s) in 0.0210 seconds
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira