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

Posted to commits@cassandra.apache.org by "Alex Petrov (Jira)" <ji...@apache.org> on 2022/01/11 16:01:00 UTC

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

    [ https://issues.apache.org/jira/browse/CASSANDRA-17248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17472852#comment-17472852 ] 

Alex Petrov commented on CASSANDRA-17248:
-----------------------------------------

Preliminary patches (CI pending):

|17248-3.0|[https://github.com/apache/cassandra/pull/1383]|[https://app.circleci.com/pipelines/github/ifesdjeen/cassandra?branch=17248-3.0]|
|17248-3.11|[https://github.com/apache/cassandra/pull/1394]|[https://app.circleci.com/pipelines/github/ifesdjeen/cassandra?branch=17248-3.11]|
|17248-4.0|[https://github.com/apache/cassandra/pull/1393]|[https://app.circleci.com/pipelines/github/ifesdjeen/cassandra?branch=17248-4.0]|


> Fix Prepared Statements behaviours after 15252
> ----------------------------------------------
>
>                 Key: CASSANDRA-17248
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17248
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Alex Petrov
>            Priority: Normal
>
> [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.1#820001)

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