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

Cameron Zemek commented on CASSANDRA-17248:
-------------------------------------------

[~smiklosovic] I haven't had time to test that pull request. However, just 
reviewing it I see it makes the same important change that I did:
{code:java}
return storePreparedStatement(queryString, clientState.getRawKeyspace(), 
prepared, forThrift); {code}
which is what the prior behaviour was before the change. Therefore, I would say 
the ticket CASSANDRA-20350 that I made is a duplicate of this one.

 

The customer was upgrading from 3.11.10 to 3.11.15 when they encountered the 
issue. They reported error:
{noformat}
java.lang.IllegalStateException / ID mismatch while trying to reprepare 
(expected **********, got **********). This prepared statement won't work 
anymore. This usually happens when you run a 'USE...' query after the statement 
was prepare{noformat}

> 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

Reply via email to