[ https://issues.apache.org/jira/browse/CASSANDRA-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14631446#comment-14631446 ]
Sylvain Lebresne commented on CASSANDRA-6477: --------------------------------------------- bq. why not also pair it with RF-2 (or 1, and only support RF=3 for now) partners, to whom it requires the first write to be propagated, without which it does not acknowledge? This could be done with a specialised batchlog write, that goes to the local node and the paired MV node. I _think_ I get a vague idea of what you mean but I'm not fully sure (and I'm not fully sure it's practical). So lets first make sure I understand. Is the suggestion that to guarantee that if base-table replica applies an update, then RF/2 other ones also do it, we'd send the update to all base table replicas "normally" (without coordinator batchlog), but each replica would 1) write the update to a local-only batchlog and 2) forward the update to RF/2 other base table replicas? > 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)