[
https://issues.apache.org/jira/browse/CASSANDRA-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14631436#comment-14631436
]
Sylvain Lebresne commented on CASSANDRA-6477:
---------------------------------------------
bq. Pedantically you are correct. Which is why I said "effectively" and not
"literally."
Well, I mean, CL is always more about "when does we answer the client" than
"what amount of work we do internally". Every write is always written to every
replica for instance, the CL is just a matter of how long we wait before
answering the client. I'm arguing this is very exactly the case here too.
Anyway, your "the other side of that coin" made it sounds like we were doing
unusual regarding the CL, something that may not be desirable. I don't
understand what that is if that's the case.
> Materialized Views (was: Global Indexes)
> ----------------------------------------
>
> Key: CASSANDRA-6477
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6477
> Project: Cassandra
> Issue Type: New Feature
> Components: API, Core
> Reporter: Jonathan Ellis
> Assignee: Carl Yeksigian
> Labels: cql
> Fix For: 3.0 beta 1
>
> Attachments: test-view-data.sh, users.yaml
>
>
> Local indexes are suitable for low-cardinality data, where spreading the
> index across the cluster is a Good Thing. However, for high-cardinality
> data, local indexes require querying most nodes in the cluster even if only a
> handful of rows is returned.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
