You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2010/01/07 07:19:54 UTC
[jira] Commented: (CASSANDRA-678) row-level cache
[ https://issues.apache.org/jira/browse/CASSANDRA-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797533#action_12797533 ]
Jonathan Ellis commented on CASSANDRA-678:
------------------------------------------
I have the basic functionality working for reads now. Next: cache invalidation on insert.
> row-level cache
> ---------------
>
> Key: CASSANDRA-678
> URL: https://issues.apache.org/jira/browse/CASSANDRA-678
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Priority: Minor
> Fix For: 0.9
>
>
> We have a key cache but that doesn't help mitigate the expensive deserialization of the actual data to return.
> Adding a row-level cache should be fairly simple using a ConcurrentLinkedHashMap<String [key], ColumnFamily> structure. (We will only cache whole rows at a time, since already know how to query on those in-memory. This limits us to CFs full of narrow rows but that is a common enough use case to be worth tackling if it can be done simply enough.)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.