Re: MATERIALIZED VIEW difference in 3.0.3 to 3.0.7/3.7

Hi Michael, CASSANDRA-9928 has open discussion . And our use case is also similar to the follow ups mentioned in this jira. We update all columns together which are used in MV key.

Re: MATERIALIZED VIEW difference in 3.0.3 to 3.0.7/3.7

It turns out this behaviour was not intended to be allowed and constructing MVs like this can lead to issues. See https://issues.apache.org/jira/browse/CASSANDRA-9928 -- Michael Mior michael.m...@gmail.com 2016-06-21 7:32 GMT-04:00 Atul Saroha : > There is behavioural

Re: MATERIALIZED VIEW difference in 3.0.3 to 3.0.7/3.7

This appears to be a bug introduced in some refactoring of the materialized view code. I logged CASSANDRA-12044 for this. https://issues.apache.org/jira/browse/CASSANDRA-12044 -- Michael Mior michael.m...@gmail.com 2016-06-21 7:32 GMT-04:00 Atul Saroha : > There is

MATERIALIZED VIEW difference in 3.0.3 to 3.0.7/3.7

There is behavioural difference between 3.0.3 and (3.0.7/3.7) for below schema in materialized view. CREATE TABLE ks.pa ( > id bigint, > sub_id text, > name text, > class text, > r_id bigint, > k_id bigint, > created timestamp, > priority int, > updated