Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 221CECAEF for ; Sun, 27 May 2012 19:05:24 +0000 (UTC) Received: (qmail 20367 invoked by uid 500); 27 May 2012 19:05:23 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 20341 invoked by uid 500); 27 May 2012 19:05:23 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 20333 invoked by uid 99); 27 May 2012 19:05:23 -0000 Received: from issues-vm.apache.org (HELO issues-vm) (140.211.11.160) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 27 May 2012 19:05:23 +0000 Received: from isssues-vm.apache.org (localhost [127.0.0.1]) by issues-vm (Postfix) with ESMTP id 450C41402B8 for ; Sun, 27 May 2012 19:05:23 +0000 (UTC) Date: Sun, 27 May 2012 19:05:22 +0000 (UTC) From: "Andrew Purtell (JIRA)" To: issues@hbase.apache.org Message-ID: <1157510545.7330.1338145523289.JavaMail.jiratomcat@issues-vm> Subject: [jira] [Created] (HBASE-6114) CacheControl flags should be tunable per table schema per CF MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Andrew Purtell created HBASE-6114: ------------------------------------- Summary: 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 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. -- 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