[ https://issues.apache.org/jira/browse/HBASE-6114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell updated HBASE-6114: ---------------------------------- Comment: was deleted (was: -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12530143/6114-0.92-v2.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 new or modified tests. -1 patch. The patch command could not apply the patch. Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/2045//console This message is automatically generated.) > 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-v2.patch, 6114-0.92.patch, 6114-0.94-v2.patch, > 6114-0.94.patch, 6114-trunk-v2.patch, 6114-trunk.patch, 6114.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