[
https://issues.apache.org/jira/browse/CASSANDRA-16172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paulo Motta updated CASSANDRA-16172:
------------------------------------
Bug Category: Parent values: Correctness(12982)Level 1 values: Recoverable
Corruption / Loss(12986)
Complexity: Challenging
Discovered By: User Report
Severity: Normal
> materialized view can return stale data even with R+W>N
> -------------------------------------------------------
>
> Key: CASSANDRA-16172
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16172
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Materialized Views
> Reporter: Zhao Yang
> Priority: Normal
> Fix For: 4.x
>
>
> This is a similar issue as CASSANDRA-8272.
> With a key-value table on a 2-node cluster with RF2 and there is a MV that
> put `value` as partition key.
> Insert with ConsistencyLevel.ONE twice with different data, assuming there is
> a network partition between 2 nodes:
> - Node 1 received: pk="a" -> value=1 @ts1
> - Node 2 received: pk="a" -> value=2 @ts2 where ts2 > ts1
> When querying `value`=1 on MV with ConsistencyLevel.ALL, we got stale row:
> "a" -> 1.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
