[
https://issues.apache.org/jira/browse/CASSANDRA-10965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226206#comment-15226206
]
Sylvain Lebresne commented on CASSANDRA-10965:
----------------------------------------------
I don't think that change is sufficient in practice, but the why requires a bit
of context and it's all in CASSANDRA-11500. Basically, I like to think of this
case is a nasty special case of CASSANDRA-11500 so it might be as simple to
just handle both side of the project in CASSANDRA-11500.
I'll note that the repro script of this ticket actually doesn't fail on
CASSANDRA-11475 due to difference with how the deletion timestamp is picked,
but it's easy to add one more step to this test to reproduce a similar problem.
So CASSANDRA-11475 doesn't really solve this, it just make it a little harder
to run into.
> 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)
