[
https://issues.apache.org/jira/browse/HBASE-20045?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16372487#comment-16372487
]
Anoop Sam John commented on HBASE-20045:
----------------------------------------
When cache on write config is ON, we will cache all the blocks from the newly
written file. The file can be new flushed one or a new compacted result file.
(Am I correct only?) So what you suggest is selectively cache the blocks of
these newly compacted result file? Only some recent data is getting cached.
If the block contain only very old data (like older than 24 hrs) dont cache it
on write. But if some newer data in block, cache it. Am I reading it correct
JMS?
> When running compaction, cache recent blocks.
> ---------------------------------------------
>
> Key: HBASE-20045
> URL: https://issues.apache.org/jira/browse/HBASE-20045
> Project: HBase
> Issue Type: New Feature
> Components: BlockCache, Compaction
> Affects Versions: 2.0.0-beta-1
> Reporter: Jean-Marc Spaggiari
> Priority: Major
>
> HBase already allows to cache blocks on flush. This is very useful for
> usecases where most queries are against recent data. However, as soon as
> their is a compaction, those blocks are evicted. It will be interesting to
> have a table level parameter to say "When compacting, cache blocks less than
> 24 hours old". That way, when running compaction, all blocks where some data
> are less than 24h hold, will be automatically cached.
>
> Very useful for table design where there is TS in the key but a long history
> (Like a year of sensor data).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
