[
https://issues.apache.org/jira/browse/CASSANDRA-13798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16141792#comment-16141792
]
ZhaoYang commented on CASSANDRA-13798:
--------------------------------------
This ticket is to block creating new table with non-pk base column filtering.
All internal filter related logic are still there for supporting filter
conditions on base pk. (existed even before CASSANDRA-10368)
Existing users of 3.10/3.11 with non-pk base column should still be able to
successfully upgrade and use the broken non-pk base column filtering.(
probably, we should give them an option to avoid filtering as well..).
> 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: [email protected]
For additional commands, e-mail: [email protected]
