[
https://issues.apache.org/jira/browse/CASSANDRA-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14631472#comment-14631472
]
Sylvain Lebresne commented on CASSANDRA-6477:
---------------------------------------------
bq. So it makes sense to have replication paired.
Sure, didn't implied otherwise, I just wasn't aware we were doing it.
bq. I do think waiting for the MV updates to be synchronous will cause a lot
more timeouts and write latency (on top of what we have now).But if it's
optional then people can choose.
Frankly, I'm pretty negative on adding such option. I think there is some basic
guarantees that shouldn't be optional, and the CL ones are amongst those.
Making it optional will have people shoot themselves in the foo all the time.
At the very least, I would aks that we don't include such option on this ticket
(there is enough stuff to deal with) and open a separate ticket to discuss it
(one on which we'd actually benchmark thinks before assuming there will be
timeouts).
> 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)
