cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vijay (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5357) Query cache
Date Mon, 15 Apr 2013 02:16:16 GMT


Vijay commented on CASSANDRA-5357:

None... but the idea is that we will compact/drop the rows (based on the LRU algo). 

Kind of the same reason memcache does for its memory to avoid fragmentation.
Good thing is we already have a better way to manage compaction.

At this point i dont know if it is a overkill to complicate.
But if there is enough support i can give it a shot :)
> Query cache
> -----------
>                 Key: CASSANDRA-5357
>                 URL:
>             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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message