[
https://issues.apache.org/jira/browse/CASSANDRA-9928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14965509#comment-14965509
]
Tyler Hobbs edited comment on CASSANDRA-9928 at 10/20/15 9:02 PM:
------------------------------------------------------------------
One possible solution is to require that all non-PK columns that are in a view
PK be updated simultaneously. [~tjake] mentioned possible problems from read
repair, but it seems like with this restriction in place, any read repairs
would end up repairing all non-PK columns at once.
This would also solve (or avoid) CASSANDRA-10226.
was (Author: thobbs):
One possible solution is to require that all non-PK columns that are in a view
PK be updated simultaneously. [~tjake] mentioned possible problems from read
repair, but it seems like with this restriction in place, any read repairs
would end up repairing all non-PK columns at once.
> Add Support for multiple non-primary key columns in Materialized View primary
> keys
> ----------------------------------------------------------------------------------
>
> Key: CASSANDRA-9928
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9928
> Project: Cassandra
> Issue Type: Improvement
> Reporter: T Jake Luciani
> Labels: materializedviews
> Fix For: 3.x
>
>
> Currently we don't allow > 1 non primary key from the base table in a MV
> primary key. We should remove this restriction assuming we continue
> filtering out nulls. With allowing nulls in the MV columns there are a lot
> of multiplicative implications we need to think through.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
