[
https://issues.apache.org/jira/browse/CASSANDRA-20634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17951261#comment-17951261
]
David Capwell commented on CASSANDRA-20634:
-------------------------------------------
Feel free to reach out. There are logically 2 different steps
1) update the randomness to include range tombstones. This is in ASTGenerators
and already has logic to pick what type of delete to do. There you would add
range support for clustering when this type of delete is selected
2) update model to understand. The model supports timestamps but doesn’t allow
“time travel” so all things are expected to be sequential, this means a range
delete just delete anything matching
> Extend ASTSingleTableModel and ASTGenerators to support range tombstones
> ------------------------------------------------------------------------
>
> Key: CASSANDRA-20634
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20634
> Project: Apache Cassandra
> Issue Type: Improvement
> Components: Test/fuzz
> Reporter: Caleb Rackliffe
> Assignee: Sunil Ramchandra Pawar
> Priority: Normal
> Fix For: 5.x
>
>
> One of the remaining blind spots for the AST-based fuzz tests is range
> deletes. We should be able to add support for them via the WHERE clause of
> {{Delete}} mutations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
