[
https://issues.apache.org/jira/browse/CASSANDRA-20830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18015692#comment-18015692
]
David Capwell edited comment on CASSANDRA-20830 at 8/22/25 4:16 PM:
--------------------------------------------------------------------
bq. is that historical problems like CASSANDRA-19007 might not be possible due
to the way filtering queries work with MT.
if the test removes
"org.apache.cassandra.cql3.KnownIssue#AF_MULTI_NODE_MULTI_COLUMN_AND_NODE_LOCAL_WRITES"
from the IGNORED_ISSUES set, then that assumption will be tested.
was (Author: dcapwell):
bg. is that historical problems like CASSANDRA-19007 might not be possible due
to the way filtering queries work with MT.
if the test removes
"org.apache.cassandra.cql3.KnownIssue#AF_MULTI_NODE_MULTI_COLUMN_AND_NODE_LOCAL_WRITES"
from the IGNORED_ISSUES set, then that assumption will be tested.
> 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]
