[
https://issues.apache.org/jira/browse/CASSANDRA-5357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13865383#comment-13865383
]
Jonathan Ellis commented on CASSANDRA-5357:
-------------------------------------------
bq. It seems to me that this reasoning apply equally well to the current row
cache.
It would, but the current row cache is dangerous enough that I don't want to
spend effort making it smarter. :)
bq. I do think we really should maintain a global limit on how much is cached
Agreed 100%; I'm just saying we should apportion that to the CFs based on our
metrics.
In any case, I'm getting ahead of what we should focus on for 2.1.0 here.
> Query cache / partition head cache
> ----------------------------------
>
> Key: CASSANDRA-5357
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5357
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Jonathan Ellis
> Assignee: Marcus Eriksson
> Fix For: 2.1
>
>
> 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.5#6160)
