[CASSANDRA-18981] Add a mechanism to signal that a rejected Transformation should not be retried

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: NA
• Component/s: Transactional Cluster Metadata
• Epic Link: CEP-21: TCM
• Change Category: Semantic
• Complexity: Normal
• Platform: All

Source Control Link

https://github.com/apache/cassandra/commit/3c06fffa4a0b1536973ab83c72726c4d4236d898

Test and Documentation Plan

CI

• Assignee: Alex Petrov Assign to me
• Reporter: Sam Tunnicliffe

Authors

Alex Petrov

Reviewers

Marcus Eriksson, Sam Tunnicliffe

• Created: 31/Oct/23 12:10
• Updated: 16/Nov/23 16:46
• Resolved: 16/Nov/23 16:46

Description

In certain circumstances on the CMS node, it is useful to be able to cause a Transformation being applied to return a Rejected response without triggering catchup and retry. Adding an unchecked exception type for this enables it to be triggered from anywhere within the call stack, without polluting the interfaces.

Implementation can be found in:
https://github.com/beobal/cassandra/commit/8a84c0b562d59487a4c5fe7c8fb233cba3036216

CI summary results attached. For right now, we've only been foccussing on unit tests, in-jvm & python dtests, so the failures in other suites are to be expected. Unfortunately, the archive containing the detailed results is too large to attach as a single file, so will look into the best way to work around that.
The intention is to fix all suites before merging the feature branch.

Suite	Total	Passed	Skipped	Failed	Errors
jvm dtest	1508	1465	24	8	11
python dtest	1083	790	262	28	3
unit	12082	12006	61	6	9