[
https://issues.apache.org/jira/browse/CASSANDRA-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14616856#comment-14616856
]
Carl Yeksigian commented on CASSANDRA-6477:
-------------------------------------------
[~aboudreault]: This was an unrelated issue - it was related to keeping track
whether the MV was built or not; I'm still looking at what is causing the
inconsistency when a new node has been added. I have only seen it occur once in
my testing, but it would be good to catch.
[~iamaleksey]: I haven't done any cstar testing yet; have only done local
stress. Would be good to run that, though I don't think we can run it through
the web interface as we'll need to create the MV. /cc [~enigmacurry]
> 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)
