[CASSANDRA-17248] Fix Prepared Statements behaviours after 15252

• Type: Bug
• Status: In Progress
• Priority: Normal
• Resolution: Unresolved
• Fix Version/s: 3.0.26, 3.11.12, 4.0.2
• Component/s: Messaging/Client
• Bug Category: Correctness - Recoverable Corruption / Loss
• Severity: Critical
• Complexity: Challenging
• Discovered By: Fuzz Test
• Platform: All
• Since Version: 3.0.25

Source Control Link

https://github.com/apache/cassandra/commit/242f7f9b18db77bce36c9bba00b2acda4ff3209e

Test and Documentation Plan

Tests included. 3.0 and 3.11 branches were also tested with mixed mode tester separately, but commit was not included since it required a change in driver version to work. It is included in 4.0 and trunk

• Assignee: Unassigned
• Reporter: Alex Petrov

Reviewers

Alex Petrov, Marcus Eriksson

• Created: 10/Jan/22 14:53
• Updated: 25/Jan/24 07:02

Description

CASSANDRA-15252 has fixed an important issue: unwanted hash changes when preparing fully qualified prepared statements which was causing cluster-killing re-prepare loops. However, the fix introduced a regression: non-qualified statements can get prepared against one keyspace but then executed on another under some circumstances. This patch reconciles all behaviours.