cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paulo Motta (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-13798) Disallow filtering on non-primary-key base column for MV
Date Tue, 29 Aug 2017 08:08:01 GMT

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

Paulo Motta commented on CASSANDRA-13798:
-----------------------------------------

bq. Right OK. If we can do it in 4.1 that's fine. It seems we don't actually have a difference
between major and minor then? My (incorrect) assumption was that massive storage changes constituted
a major version change, and 4.x would be intended to be minor.

Hmm it depends whether the tick tock model is happening or not after 4.0, I'm not sure what
the consensus was with that. But I meant that sstable version changes are normally during
majors, and assumed 4.1 would be a major in the non-tick model while 4.0.1 would be a minor
(following the previous model). In any case, this is just to leave things at a consistent
state in case the community decides to release 4.0 without waiting for this feature to be
fully enabled, but doesn't prevent us to removing this limitation if the feature is correctly
implemented by 4.0 release timeframe. We will create another ticket to properly enable this
feature following this.

> 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