Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 5 Oct 2011 01:27:35 +0000 (UTC)
From: "Jonathan Gray (Commented) (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: 
 <27969934.10312.1317778055201.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <927471525.36309.1316205128992.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HBASE-4422) Move block cache parameters and
 references into single CacheConf class
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Gray commented on HBASE-4422:
--------------------------------------

Yeah, if this goes to trunk but not 92 then begins the fun of rebasing patches for each because it changes so many constructors in/around HFile.
                
> Move block cache parameters and references into single CacheConf class
> ----------------------------------------------------------------------
>
>                 Key: HBASE-4422
>                 URL: https://issues.apache.org/jira/browse/HBASE-4422
>             Project: HBase
>          Issue Type: Improvement
>          Components: io
>            Reporter: Jonathan Gray
>            Assignee: Jonathan Gray
>             Fix For: 0.92.0
>
>         Attachments: CacheConfig92-v8.patch
>
>
> From StoreFile down to HFile, we currently use a boolean argument for each of the various block cache configuration parameters that exist.  The number of parameters is going to continue to increase as we look at compressed cache, delta encoding, and more specific L1/L2 configuration.  Every new config currently requires changing many constructors because it introduces a new boolean.
> We should move everything into a single class so that modifications are much less disruptive.

--
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