[CASSANDRA-20126] Fix RequestFailureReason.READ_TOO_MANY_INDEXES in trunk

• Type: Bug
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 5.1-alpha, 5.1
• Component/s: Local/Other
• Bug Category: Code - Bug - Unclear Impact
• Severity: Low
• Complexity: Low Hanging Fruit
• Discovered By: User Report
• Platform: All

Source Control Link

https://github.com/apache/cassandra/commit/bc40d3bb27cac7979867def92fe84e5fa5011155

Test and Documentation Plan

Patch: https://github.com/apache/cassandra/pull/3725

JDK 11 CI running here: https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/2737/workflows/0e7ea6ab-643e-4d73-b3a7-6a7ac0d27c63

• Assignee: Ekaterina Dimitrova
• Reporter: Ekaterina Dimitrova

Authors

Ekaterina Dimitrova

Reviewers

Caleb Rackliffe, Ekaterina Dimitrova, Stefan Miklosovic

• Created: 04/Dec/24 17:21
• Updated: 05/Dec/24 20:39
• Resolved: 05/Dec/24 20:39

Description

RequestFailureReason.READ_TOO_MANY_INDEXES - the code for it is 7 in cassandra-5.0. That has changed probably by mistake or because of merge conflict in trunk. Now the code is 10. This is breaking change. The fix will be just assign code 7 to RequestFailureReason.READ_TOO_MANY_INDEXES and move down all the new reasons added to their current trunk code+1 in trunk. This change is OK because we haven't had a release from trunk yet. 

 

Issue Links

• links to: GitHub Pull Request #3725