cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Roth (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13798) Disallow filtering on non-primary-key base column for MV
Date Fri, 25 Aug 2017 14:04:00 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-13798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16141663#comment-16141663
] 

Benjamin Roth commented on CASSANDRA-13798:
-------------------------------------------

Even if the current implementation has known issues, you cannot kill that (or any other) feature
just like that. As [~JoshuaMcKenzie] mentioned, how do you treat existing installations +
schemas?
If I was affected (I really have to check this) this would either force me to change my schema
or to be blocked on updates. Both is not viable if the current solution works for my needs.
For example I am not really affected if I have an insert-only payload or if my data does not
expire.

What you of course can do: 
Spit our a warning in the logs on bootstrap if the schema is affected and on schema changes
that are affected and refer to a JIRA. So one can decide to stay with it or to migrate the
schema / model to be not affected any more.

My 2 cents.

> Disallow filtering on non-primary-key base column for MV
> --------------------------------------------------------
>
>                 Key: CASSANDRA-13798
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13798
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Materialized Views
>            Reporter: ZhaoYang
>            Assignee: ZhaoYang
>
> We should probably consider disallow filtering conditions on non-primary-key base column
for Materialized View which is introduced in CASSANDRA-10368.
> The main problem is that the liveness of view row is now depending on multiple base columns
(multiple filtered non-pk base column + base column used in view pk) and this semantic could
not be properly support without drastic storage format changes. (SEE CASSANDRA-11500, [background|https://issues.apache.org/jira/browse/CASSANDRA-11500?focusedCommentId=16119823&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16119823])
> We should step back and re-consider the non-primary-key filtering feature together with
supporting multiple non-PK cols in MV clustering key in CASSANDRA-10226.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message