[
https://issues.apache.org/jira/browse/CASSANDRA-5357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13845899#comment-13845899
]
Jonathan Ellis commented on CASSANDRA-5357:
-------------------------------------------
bq. only cache the head of the row and it's bounds
That's a very interesting idea, and a good fit with existing best practices
("slicing from the start of the partition is fastest").
I think we could also do some intelligent sizing of the cache per-CF with the
metrics we keep, that would be relatively static (so impervious to churn).
With the query cache the best we can do is LRU.
WDYT [~pmcfadin] [~tupshin]?
> Query cache
> -----------
>
> Key: CASSANDRA-5357
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5357
> Project: Cassandra
> Issue Type: Bug
> Reporter: Jonathan Ellis
> Assignee: Vijay
>
> I think that most people expect the row cache to act like a query cache,
> because that's a reasonable model. Caching the entire partition is, in
> retrospect, not really reasonable, so it's not surprising that it catches
> people off guard, especially given the confusion we've inflicted on ourselves
> as to what a "row" constitutes.
> I propose replacing it with a true query cache.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
