[
https://issues.apache.org/jira/browse/CASSANDRA-17248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17929129#comment-17929129
]
Stefan Miklosovic commented on CASSANDRA-17248:
-----------------------------------------------
I took the patch of [~chovatia.jayd...@gmail.com] for 3.0 and ported it to 3.11
here (1). I have kept "warnAboutUseWithPreparedStatements" in place as
suggested by [~ifesdjeen] in his last comment.
[~cam1982] is this solving your problem?
(1) https://github.com/apache/cassandra/pull/3919
> Fix Prepared Statements behaviours after 15252
> ----------------------------------------------
>
> Key: CASSANDRA-17248
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17248
> Project: Apache Cassandra
> Issue Type: Bug
> Components: Messaging/Client
> Reporter: Alex Petrov
> Priority: Normal
> Fix For: 3.0.26, 3.11.12, 4.0.2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> [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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
