[
https://issues.apache.org/jira/browse/CASSANDRA-10755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ZhaoYang resolved CASSANDRA-10755.
----------------------------------
Resolution: Not A Problem
Because C* instance is started with "file.encoding=ANSI_X3.4-1968" , UTF8 can
solve it
> PreparedStatement is the same id for different Japanese katakana characters
> with same length
> --------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-10755
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10755
> Project: Cassandra
> Issue Type: Bug
> Environment: cassandra-2.1.8, java driver 2.1.5, ubuntu 14.04
> Reporter: ZhaoYang
>
> 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?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
