[
https://issues.apache.org/jira/browse/CASSANDRA-9928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16088582#comment-16088582
]
Fridtjof Sander commented on CASSANDRA-9928:
--------------------------------------------
I seem to be the only one, who doesn't understanding where the actual
difference to the single-column case is:
Consider {{(p=1, a=1)}} with an index-MV on {{a}} and two updates {{a=2}} and
{{a=3}}. One base-replica receives {{a=2}}, deletes view entry {{(a=1, p=1)}}
and inserts {{(a=2, p=1)}}, then dies. Other base-replicas get {{a=3}}, delete
{{(a=1, p=1)}} and insert {{(a=3, p=1)}}. Now, how is {{(a=2, p=1)}} removed
from the view replica that was paired with the dying base-node? I don't get
what's different here. Or does my analog case miss the point?
> 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: 4.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.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
