[
https://issues.apache.org/jira/browse/CASSANDRA-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14612091#comment-14612091
]
Alan Boudreault commented on CASSANDRA-6477:
--------------------------------------------
While testing, I noticed that if we drop a column that is used by a
materialized view (PK), the view is dropped silently. It looks like it's the
desired behavior since a log entry is written saying: "
MigrationManager.java:381 - Drop table 'ks/users_by_state'".
I just wanted to raise a suggestion: would it better (and possible) to force
the user to delete its materialize view explicitly before doing this operation,
rather than dropping the MV silently? Not a strong opinion here, I'm just
thinking that this could be annoying for users to notice some MV disappeared.
> 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)
