[
https://issues.apache.org/jira/browse/CASSANDRA-5357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13626735#comment-13626735
]
Jonathan Ellis commented on CASSANDRA-5357:
-------------------------------------------
bq. What i had in mind was to do something like Map<RowKey,
[QueryFilter,ColumnFamily]> so invalidation is O(1). To further improve the
performance on a query (And deserializing the whole [QueryFilter,ColumnFamily]
we can have all the QueryFilters as a part of the RowKey (Kind of like promoted
index's).
I don't follow -- how can you have both O(1) [Map key is the row key] and also
promote QF into the key?
bq. If we do this then the K (For a fat row) becomes big enough to cause more
heap issue. Hence we could move that to off-heap along with CF.
We're talking about K=Map Key, right? How do you see QF increasing by row size?
> 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
