cassandra-commits mailing list archives

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

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

Kurt Greaves commented on CASSANDRA-13798:
------------------------------------------

I think something should be done on 3.11 and blocking the behaviour with a workaround flag
as [~pauloricardomg] suggested is probably the best way to go about it. MV's are already causing
a lot of issues for people doing dev on 3.11, and I know we have users with this case, that
will undoubtedly run into issues sooner or later.

However I'm not convinced about also committing this to 4.0. If we're not committing to fixing
it in 4.0 then MV's will be pretty useless until 5.0 if it does take massive storage changes,
which could be a long way away. Which will be problematic for people who have already gone
down this path, and we'll be missing a much wanted feature for quite a long time. IMO we made
the mistake of pushing it out too fast, we should fix it asap.

> 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