[
https://issues.apache.org/jira/browse/CASSANDRA-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14662980#comment-14662980
]
Benedict commented on CASSANDRA-6477:
-------------------------------------
I'm just wondering if any thought has been given to weird race conditions on
schema changes here. It looks like we open the MV by name, so could there not
be some weird sequence of drop/create table/MV that results in the cluster
thinking the MV is two different CFs until nodes reboot?
I haven't thought about it much, so it might be benign, it just looks like a
race that won't be fixed by the schema improvements [~iamaleksey] is working on
> 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 alpha 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)
