hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6114) CacheControl flags should be tunable per table schema per CF
Date Wed, 30 May 2012 09:18:23 GMT

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

Hudson commented on HBASE-6114:
-------------------------------

Integrated in HBase-0.92 #431 (See [https://builds.apache.org/job/HBase-0.92/431/])
    HBASE-6114. CacheControl flags should be tunable per table schema per CF (Revision 1344107)

     Result = SUCCESS
apurtell : 
Files : 
* /hbase/branches/0.92/CHANGES.txt
* /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/HColumnDescriptor.java
* /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/io/hfile/CacheConfig.java
* /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/regionserver/Store.java
* /hbase/branches/0.92/src/test/java/org/apache/hadoop/hbase/regionserver/TestCacheOnWriteInSchema.java

                
> 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
>             Fix For: 0.92.2, 0.96.0, 0.94.1
>
>         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

        

Mime
View raw message