[
https://issues.apache.org/jira/browse/CASSANDRA-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14633392#comment-14633392
]
Sylvain Lebresne commented on CASSANDRA-6477:
---------------------------------------------
bq. Also we should expose the base -> view replica pairs so operators know
which ones need to be rebuilt.
Talking of that pairing, do we properly take care of topology changes? That is,
when the ownership of some of the range is moving from a MV replica A to some
other not B (that is bootstrapping for instance), do we make sure to send the
MV update to both node A and B (and we probably need to make such check on each
replay of the local batch log)?
> 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)
