[
https://issues.apache.org/jira/browse/HBASE-7236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Shelukhin updated HBASE-7236:
------------------------------------
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).
was:
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:
{code}
alter 'mytable', CONFIGURATION =>
{'hbase.hregion.scan.loadColumnFamiliesOnDemand' => 'true'}
alter 'mytable', {NAME => 'mycolumnfamily', CONFIGURATION =>
{'hbase.hstore.blockingStoreFiles' => '10'}}
{code}.
You can also do it programmatically by modifying HTableDescriptor and
HColumnDescriptor for create and alter operations (setConfiguration method).
> add per-table/per-cf configuration via metadata
> -----------------------------------------------
>
> Key: HBASE-7236
> URL: https://issues.apache.org/jira/browse/HBASE-7236
> Project: HBase
> Issue Type: Umbrella
> Affects Versions: 0.95.2
> Reporter: Sergey Shelukhin
> Assignee: Sergey Shelukhin
> Fix For: 0.95.0
>
> Attachments: HBASE-7236-PROTOTYPE.patch, HBASE-7236-PROTOTYPE.patch,
> HBASE-7236-PROTOTYPE-v1.patch, HBASE-7236-v0.patch, HBASE-7236-v1.patch,
> HBASE-7236-v2.patch, HBASE-7236-v3.patch, HBASE-7236-v4.patch,
> HBASE-7236-v5.patch, HBASE-7236-v6.patch, HBASE-7236-v6.patch
>
>
> 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.
--
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
