[ https://issues.apache.org/jira/browse/CASSANDRA-10965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15090159#comment-15090159 ]
Taiyuan Zhang edited comment on CASSANDRA-10965 at 1/8/16 11:16 PM: -------------------------------------------------------------------- I ran the script, and here is the output: {code} cqlsh:mykeyspace> SELECT c, k, val FROM base; SELECT c, k, val FROM mv_reuse; c | k | val ---+---+----- 0 | 1 | 1 (1 rows) c | k | val ---+---+----- 0 | 1 | 1 (1 rows) cqlsh:mykeyspace> UPDATE base USING TIMESTAMP 1 SET c = 1 WHERE k = 1; cqlsh:mykeyspace> SELECT c, k, val FROM base; SELECT c, k, val FROM mv_reuse; c | k | val ---+---+----- 1 | 1 | 1 (1 rows) c | k | val ---+---+----- (0 rows) {code} So the problem is: after the update using the same timestamp, the row is not shown when query from the materialized view? was (Author: firstprayer): I ran the script, and here is the output: {code} cqlsh:mykeyspace> SELECT c, k, val FROM base; SELECT c, k, val FROM mv_reuse; c | k | val ---+---+----- 0 | 1 | 1 (1 rows) c | k | val ---+---+----- 0 | 1 | 1 (1 rows) cqlsh:mykeyspace> UPDATE base USING TIMESTAMP 1 SET c = 1 WHERE k = 1; cqlsh:mykeyspace> SELECT c, k, val FROM base; SELECT c, k, val FROM mv_reuse; c | k | val ---+---+----- 1 | 1 | 1 (1 rows) c | k | val ---+---+----- {code} So the problem is: after the update using the same timestamp, the row is not shown when query from the materialized view? > Shadowable tombstones can continue to shadow view results when timestamps > match > ------------------------------------------------------------------------------- > > Key: CASSANDRA-10965 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10965 > Project: Cassandra > Issue Type: Bug > Components: Local Write-Read Paths > Reporter: Carl Yeksigian > Assignee: Carl Yeksigian > Fix For: 3.0.x > > Attachments: shadow-ts.cql > > > I've attached a script which reproduces the issue. The first time we insert > with {{TIMESTAMP 2}}, we are inserting a new row which has the same timestamp > as the previous shadow tombstone, and it continues to be shadowed by that > tombstone because we shadow values with the same timestamp. -- This message was sent by Atlassian JIRA (v6.3.4#6332)