[
https://issues.apache.org/jira/browse/CASSANDRA-13798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16141763#comment-16141763
]
Paulo Motta edited comment on CASSANDRA-13798 at 8/25/17 3:43 PM:
------------------------------------------------------------------
bq. 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.
It seems from a quick peek at the patch that this just forbids creation of new
tables with non-PK conditions, but does not break existing tables. So this just
changes the UX to prevent news users from shooting themselves in the foot, but
keeps the underlying machinery to support it (which will probably be reused
when the feature is fully supported). Perhaps we can even have a hidden system
flag to allow table creation if you "know what you are doing"© and you can
guarantee there are no column updates. In any case, we should explain the
reasoning behind the revert and maybe expose the system flag for append-only
workloads on NEWS.txt.
was (Author: pauloricardomg):
bq. 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.
It seems from a quick peek at the patch that this just forbids creation of new
tables with non-PK conditions, but does not break existing tables. So this just
changes the UX to prevent users from shooting themselves in the foot, but keeps
the underlying machinery to support it (which will probably be reused when the
feature is fully supported). Perhaps we can even have a hidden system flag to
allow table creation if you "know what you are doing"© and you can guarantee
there are no column updates. In any case, we should explain the reasoning
behind the revert and maybe expose the system flag for append-only workloads on
NEWS.txt.
> 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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
