[
https://issues.apache.org/jira/browse/CASSANDRA-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632716#comment-14632716
]
Benedict commented on CASSANDRA-6477:
-------------------------------------
I don't think it's that simple. The MV data is spread across the whole cluster.
How do you know where the ghost records are, to delete them? You don't know
what the prior state was, so you can only send the current records, not remove
the old ones. Do you introduce a special "truncate" record for primary key
portions that match to our tokens? Do you rebuild the whole MV? Or am I missing
an obvious trick?
> 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)
