[ https://issues.apache.org/jira/browse/CASSANDRA-5357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13775967#comment-13775967 ]
Vijay commented on CASSANDRA-5357: ---------------------------------- {quote} I'm saying just shove the ColumnFamily payload off-heap but leave the rest "live." {quote} Sure but that can cause more memory pressure in the JVM, IMHO (cost vs benefit) its not that bad to deserialize the filters at least in the stress tests i did. {quote} I'm not sure I understand exactly how the problem happens here. {quote} The problem is when the whole row (lets say multiple MB's) column family is cached, instead of de-serializing the whole column family at once we can de-serialize it during filter in CFS.filterColumnFamily, hence the QC should return a iterator instead of CF... Makes sense? > 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