[
https://issues.apache.org/jira/browse/CASSANDRA-20830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18013513#comment-18013513
]
Caleb Rackliffe edited comment on CASSANDRA-20830 at 8/21/25 7:19 PM:
----------------------------------------------------------------------
Pushed up a new AST-based test that has begun to produce failures. It looks
like the CEP branch hasn't been rebased to trunk in a while, and there are a
few things I'm going to need from there. Going to take care of that before I
make further progress...
was (Author: maedhroz):
Pushed up the new AST-based test that produces the failure above
[here|https://github.com/apache/cassandra/pull/4303]. It looks like the CEP
branch hasn't been rebased to trunk in a while, and there are a few things I'm
going to need from there. Going to take care of that before I make further
progress here...
> AST Fuzz testing support for tables w/ mutation tracking enabled
> ----------------------------------------------------------------
>
> Key: CASSANDRA-20830
> URL: https://issues.apache.org/jira/browse/CASSANDRA-20830
> Project: Apache Cassandra
> Issue Type: Task
> Components: Consistency/Coordination
> Reporter: Caleb Rackliffe
> Assignee: Caleb Rackliffe
> Priority: Normal
> Fix For: NA
>
>
> We need to start exposing the mutation tracking work to the AST fuzz tester.
> Specifically, I think we can start with something similar to
> {{MultiNodeTableWalkWithoutReadRepairTest}}, just with tracking enabled
> rather than RR disabled, etc. The fun thing, from my initial conversations
> with [~bdeggleston], is that historical problems like CASSANDRA-19007 might
> not be possible due to the way filtering queries work with MT.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
