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

T Jake Luciani commented on CASSANDRA-9928:
-------------------------------------------

This scenario where 3 nodes won't see each others updates can't happen if we 
use the coordinator batchlog, since we guarantee at least a quorum of nodes 
will see the updates. Mentioning this for CASSANDRA-10230 

> 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)

Reply via email to