[
https://issues.apache.org/jira/browse/CASSANDRA-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14616945#comment-14616945
]
Joshua McKenzie commented on CASSANDRA-6477:
--------------------------------------------
bq. In the patch, there is no way to do a repair between the MV and the base
table other than dropping and recreating the view.
Would this be worth a follow-up ticket, or would the repair overhead / time
frame be long enough that it makes sense just to recommend people drop/recreate
MV after repair? If so, would it make sense to bolt that functionality as an
option onto the repair process?
> 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
>
>
> 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)
