[
https://issues.apache.org/jira/browse/HBASE-6114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285132#comment-13285132
]
Andrew Purtell edited comment on HBASE-6114 at 5/29/12 9:16 PM:
----------------------------------------------------------------
bq. Just going by javabean convention for methods that return boolean....
What about existing methods like CacheConfig#shouldCacheDataOnRead and
CacheConfig#shouldCacheBlockOnRead? Change those too?
Edit: Related, HCD#shouldCacheIndexOnWrite probably should be be
HCD#shouldCacheIndexesOnWrite because we have
CacheConfig#shouldCacheIndexesOnWrite.
was (Author: apurtell):
bq. Just going by javabean convention for methods that return boolean....
What about existing methods like CacheConfig#shouldCacheDataOnRead and
CacheConfig#shouldCacheBlockOnRead? Change those too?
> 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
> Affects Versions: 0.92.2, 0.96.0, 0.94.1
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Attachments: 6114-0.92.patch, 6114-0.94.patch, 6114-trunk.patch
>
>
> 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
