cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Boudreault (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-6477) Materialized Views (was: Global Indexes)
Date Thu, 02 Jul 2015 15:40:09 GMT


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: " - 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:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: API, Core
>            Reporter: Jonathan Ellis
>            Assignee: Carl Yeksigian
>              Labels: cql
>             Fix For: 3.0 beta 1
>         Attachments:
> 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

View raw message