[
https://issues.apache.org/jira/browse/HBASE-14189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14702642#comment-14702642
]
Anoop Sam John commented on HBASE-14189:
----------------------------------------
bq.private boolean cfBlockCacheEnabled;
So this indicates whether the cache on read in ON at CF level.
I see getters in HCD for the cache on read and cache compressed data. WHat abt
setters?
When cache on read is OFF at CF level but cache on write is ON, what we will
do? Ideally at that time we should not cache at read and write time. Also make
sure we have enough test coverage for all combinations. Per read level also,
user can specify whether to cache on read. If it is OFF at read level, we
should not cache the read blocks. But we may expect the block to be available
in cache and look for it in cache. (I think this is already done)
> BlockCache options should consider CF Level BlockCacheEnabled setting
> ---------------------------------------------------------------------
>
> Key: HBASE-14189
> URL: https://issues.apache.org/jira/browse/HBASE-14189
> Project: HBase
> Issue Type: Improvement
> Components: BlockCache
> Affects Versions: 2.0.0
> Reporter: Heng Chen
> Assignee: Heng Chen
> Attachments: HBASE-14189.patch, HBASE-14189_v1.patch
>
>
> While using BlockCache, we use {{cacheDataOnRead}}({{cacheDataOnWrite}})
> represents for whether we should cache block after read(write) block from(to)
> hdfs. We should honour BC setting and CF Level cache setting while using
> BlockCache.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
