[ https://issues.apache.org/jira/browse/HBASE-7571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sergey Shelukhin updated HBASE-7571: ------------------------------------ Release Note: >From now on, HBase settings used in region/store can be applied on column >family and table level. For the region, table and then xml settings will be >applied (i.e. table settings override xml settings). For column family >(store), column family, then table, then xml settings will be applied. Custom >metadata for column family still trumps all settings. The settings can be applied in the shell via "alter table 't', CONFIGURATION => { 'key' => 'value', .... } in a way similar to user metadata, or programmatically. The key in the above should be the same as an xml config key (e.g. "hbase.region.some.setting"). was: >From now on, HBase settings used in region/store can be applied on column >family and table level. For the region, table and then xml settings will be >applied (e.g. table settings override xml settings). For column family >(store), column family, then table, then xml settings will be applied. Custom >metadata for column family still trumps all settings. The settings can be applied in the shell via "alter table 't', CONFIGURATION => { 'key' => 'value', .... } in a way similar to user metadata, or programmatically. The key in the above should be the same as an xml config key (e.g. "hbase.region.some.setting"). > add the notion of per-table or per-column family configuration > -------------------------------------------------------------- > > Key: HBASE-7571 > URL: https://issues.apache.org/jira/browse/HBASE-7571 > Project: HBase > Issue Type: Sub-task > Reporter: Sergey Shelukhin > Assignee: Sergey Shelukhin > Attachments: 7571-v3.patch, HBASE-7571-v0-based-on-HBASE-7563.patch, > HBASE-7571-v0-including-HBASE-7563.patch, HBASE-7571-v1.patch, > HBASE-7571-v2.patch, HBASE-7571-v3.patch > > > Main part of split HBASE-7236. -- 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