[HBASE-7236] add per-table/per-cf configuration via metadata

• Type: Umbrella
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.95.2
• Fix Version/s: 0.95.0
• Labels: online_schema_change

Release Note

The ability to configure most configuration parameters per column family or table. The column family configuration overrules table configuration, which in turn overrides xml configuration. The column family metadata that was previously used still overrides any configuration.

To set configuration, you can use shell commands (see also help 'create', help 'alter'); example:
alter 'mytable', CONFIGURATION => {'hbase.hregion.scan.loadColumnFamiliesOnDemand' => 'true'}
alter 'mytable', {NAME => 'mycolumnfamily', CONFIGURATION => {'hbase.hstore.blockingStoreFiles' => '10'}}

You can also do it programmatically by modifying HTableDescriptor and HColumnDescriptor for create and alter operations (setConfiguration method).

• Assignee: Sergey Shelukhin
• Reporter: Sergey Shelukhin
• Created: 28/Nov/12 23:51
• Updated: 08/Nov/13 21:00
• Resolved: 09/Apr/13 00:52

Description

Regardless of the compaction policy, it makes sense to have separate configuration for compactions for different tables and column families, as their access patterns and workloads can be different. In particular, for tiered compactions that are being ported from 0.89-fb branch it is necessary to have, to use it properly.
We might want to add support for compaction configuration via metadata on table/cf.

Issue Links

• is related to: HBASE-7412 Fix how HTableDescriptor handles default max file size and flush size
• relates to: HBASE-5146 Hbase Shell - allow setting config properties
• relates to: HBASE-7055 port HBASE-6371 tier-based compaction from 0.89-fb to trunk (with changes)