[
https://issues.apache.org/jira/browse/CASSANDRA-13798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143483#comment-16143483
]
Paulo Motta commented on CASSANDRA-13798:
-----------------------------------------
bq. 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.
The storage changes required to support this are probably a new SSTable format
+ changes in the binary protocol, so while it requires a major version, it
doesn't need to be 5.0, but 4.1 if we are not able to ship this by 4.0.
bq. 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.
We should definitely fix this ASAP, but adding this to trunk doesn't prevent
that in any way, we're just adding this limitation while the problem is not
fixed. As a follow-up to this, we should create another ticket to implement
this feature properly. Whether that ticket should block the 4.0 release it's up
for the community to decide, but on the meantime the code will be correct in
not allowing people to use broken functionality.
> 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]
