hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6114) CacheControl flags should be tunable per table schema per CF
Date Tue, 29 May 2012 22:46:24 GMT

    [ https://issues.apache.org/jira/browse/HBASE-6114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285225#comment-13285225

Andrew Purtell commented on HBASE-6114:

bq. Maybe just commit what you have then Andrew if it is keeping the pattern set elsewhere
in this class?

Thanks, I do think HCM and CacheConfig should have the same convention for asking the same
question. Will commit in a few minutes the attached patches with Ted's comment change and
HCD#shouldCacheIndexOnWrite renamed to HCD#shouldCacheIndexesOnWrite.

> 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


View raw message