[
https://issues.apache.org/jira/browse/CASSANDRA-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628189#comment-14628189
]
Jack Krupansky commented on CASSANDRA-6477:
-------------------------------------------
What CL will apply when MV rows are deleted on TTL expiration?
Presumably each of the replicas of the base table will have its TTL expiration
triggering roughly at the same time, each local change presumably triggering a
delete of the MV, but the MV has replicas as well.
Maybe ANY is reasonable for CL for MV update on TTL since the app is not
performing an explicit operation with explicit expectations.
> 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)
