[
https://issues.apache.org/jira/browse/HBASE-6114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell updated HBASE-6114:
----------------------------------
Description:
CacheControl flags should be tunable per table schema per CF, especially
cacheDataOnWrite, also cacheIndexesOnWrite and cacheBloomsOnWrite.
It looks like Store uses CacheConfig(Configuration conf, HColumnDescriptor
family) to construct the CacheConfig, so it's a simple change there to override
configuration properties with values of table schema attributes if present.
was:
CacheControl flags should be tunable per table schema per CF, especially
hbase.rs.cacheblocksonwrite, also hfile.block.index.cacheonwrite,
io.storefile.bloom.cacheonwrite.
It looks like Store uses CacheConfig(Configuration conf, HColumnDescriptor
family) to construct the CacheConfig, so it's a simple change there to override
configuration properties with values of table schema attributes if present.
Fix Version/s: 0.94.1
0.96.0
0.92.2
> CacheControl flags should be tunable per table schema per CF
> ------------------------------------------------------------
>
> Key: HBASE-6114
> URL: https://issues.apache.org/jira/browse/HBASE-6114
> Project: HBase
> Issue Type: Improvement
> Reporter: Andrew Purtell
> Fix For: 0.92.2, 0.96.0, 0.94.1
>
>
> CacheControl flags should be tunable per table schema per CF, especially
> cacheDataOnWrite, also cacheIndexesOnWrite and cacheBloomsOnWrite.
> It looks like Store uses CacheConfig(Configuration conf, HColumnDescriptor
> family) to construct the CacheConfig, so it's a simple change there to
> override configuration properties with values of table schema attributes if
> present.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
