[
https://issues.apache.org/jira/browse/CASSANDRA-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14631420#comment-14631420
]
Sylvain Lebresne commented on CASSANDRA-6477:
---------------------------------------------
bq. But the other side of that coin is is, we're effectively promoting all
operations to at least QUORUM regardless of what the user asked for...
We're not. In the description I made above, we need to wait on QUORUM response
to remove from the batchlog, but we don't need to wait on QUORUM to respond to
the user. Unless my reasoning is broken, we do respect the CL levels exactly as
we should.
> 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)
