[
https://issues.apache.org/jira/browse/CASSANDRA-5357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13611325#comment-13611325
]
Vijay commented on CASSANDRA-5357:
----------------------------------
Hi Jonathan, What do you think about
Option 1)
A Wild idea (Just throwing it), Off-heap inmemory SSTables (SSTable like
format) and we manage compaction etc in the same way we deal with the
files....The difference is that there will be much more things to cleanup for
compaction (Like tombstones which expires immediately) :)
Option 2)
Move Query cache Keys to be a Memory Object and move the key off-heap (Only
store the hash value as the key), so the deserialization of the keys happen
only when the hash collide.... We can start with invalidation and go from there.
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
