You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Josh McKenzie (Jira)" <ji...@apache.org> on 2022/09/27 19:14:00 UTC

[jira] [Updated] (CASSANDRA-17248) Fix Prepared Statements behaviours after 15252

     [ https://issues.apache.org/jira/browse/CASSANDRA-17248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josh McKenzie updated CASSANDRA-17248:
--------------------------------------
    Resolution:     (was: Fixed)
        Status: Open  (was: Resolved)

> Fix Prepared Statements behaviours after 15252
> ----------------------------------------------
>
>                 Key: CASSANDRA-17248
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17248
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Messaging/Client
>            Reporter: Alex Petrov
>            Assignee: Alex Petrov
>            Priority: Normal
>             Fix For: 3.0.26, 3.11.12, 4.0.2
>
>
> [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.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org