[
https://issues.apache.org/jira/browse/CASSANDRA-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14631790#comment-14631790
]
Aleksey Yeschenko commented on CASSANDRA-6477:
----------------------------------------------
As an AP database that prides itself for scalability, high availability, and
decent write throughput, I don't see how we can ship with sync - a requirement
that obliterates both availability and throughput - at least by default.
*Maybe* there is a place for a second per-query CL parameter (they way we have
with LWT queries), that would specify a CL for MV mutatations (that would
default to {{ANY}}), maybe not.
> 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)
