[CASSANDRA-10755] PreparedStatement is the same id for different Japanese katakana characters with same length - ASF JIRA

XML

Word

Printable

JSON

String q1 = "UPDATE table SET value='タニャア' WHERE key=? AND key2=?";
String q2 = "UPDATE table SET value='ャアタニ' WHERE key=? AND key2=?";

when using session.prepare().

q1 and q2 will return the prepared-statement with the same prepared ID, but the query in prepared-statement is correct.

So if I update using q1 first, all later q2 will not be able to update.( It's means , it still updates q1)

Please note that the Japanese katakana is the same length in q1 and q2.
I know it's a bad use case for putting value into prepared-query itself.

Is it related to how Cassandra cache prepared statement?

is duplicated by

CASSANDRA-10539 Different encodings used between nodes can cause inconsistently generated prepared statement ids

links to

cassandra-2.2