[
https://issues.apache.org/jira/browse/CASSANDRA-10965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15109829#comment-15109829
]
Taiyuan Zhang commented on CASSANDRA-10965:
-------------------------------------------
It's been a while and it seems the output of the given cql is changed:
When I execute
{code}
INSERT INTO base (k, c, val) VALUES (1, 1, 1) USING TIMESTAMP 0;
SELECT c, k, val FROM base; SELECT c, k, val FROM mv_reuse;
UPDATE base USING TIMESTAMP 1 SET c = 0 WHERE k = 1;
SELECT c, k, val FROM base; SELECT c, k, val FROM mv_reuse;
UPDATE base USING TIMESTAMP 1 SET c = 1 WHERE k = 1;
{code}
The output is
{code}
cqlsh:mykeyspace> INSERT INTO base (k, c, val) VALUES (1, 1, 1) USING TIMESTAMP
0;
cqlsh:mykeyspace> select * FROM mv_reuse ; SELECT * FROM mv_reuse ;
k | c | val
---+---+-----
1 | 1 | 1
(1 rows)
k | c | val
---+---+-----
1 | 1 | 1
(1 rows)
cqlsh:mykeyspace> UPDATE base USING TIMESTAMP 1 SET c = 0 WHERE k = 1;
cqlsh:mykeyspace> select * FROM mv_reuse ; SELECT * FROM mv_reuse ;
k | c | val
---+---+-----
1 | 0 | 1
(1 rows)
k | c | val
---+---+-----
1 | 0 | 1
(1 rows)
cqlsh:mykeyspace> UPDATE base USING TIMESTAMP 1 SET c = 1 WHERE k = 1;
cqlsh:mykeyspace> select * FROM mv_reuse ; SELECT * FROM mv_reuse ;
k | c | val
---+---+-----
(0 rows)
k | c | val
---+---+-----
(0 rows)
{code}
So previously, the updated row will appear when selecting from the base, but
disappears when selecting from the view; now, it shows from neither select
query.
So, just to confirm, the correct, expected behavior should be: the row k=1,
c=1, val=1 should appears in BOTH select query (from base and from the view),
right?
> 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)
