cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-5357) Query cache
Date Thu, 12 Dec 2013 08:32:10 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-5357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13846150#comment-13846150
] 

Sylvain Lebresne commented on CASSANDRA-5357:
---------------------------------------------

bq. That's a very interesting idea, and a good fit with existing best practices

Isn't that pretty much exactly the initial idea for CASSANDRA-1956 (except maybe that the
"filter" would be hard-coded to "the head of the row") to which you argued that a query cache
was more generic and was handling 2ndary indexes in particular (note that I'm against the
idea, it had my preference initially if only for simplicity sake, I'm just trying to make
sure I understand the though process on this)?

> 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 was sent by Atlassian JIRA
(v6.1.4#6159)

Mime
View raw message