[
https://issues.apache.org/jira/browse/CASSANDRA-5352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne resolved CASSANDRA-5352.
-----------------------------------------
Resolution: Fixed
Fix Version/s: 1.2.3
Reviewer: slebresne
Assignee: David Sauer
Good catch. Committed with a slight modification to handle the case where the
current keyspace is {{null}}.
> PreparedStatements get mixed up between Keyspaces
> -------------------------------------------------
>
> Key: CASSANDRA-5352
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5352
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.2.2
> Reporter: David Sauer
> Assignee: David Sauer
> Fix For: 1.2.3
>
> Attachments: CassandraServerCql3Test.java, patch.txt
>
>
> I found this behavior while running the same application using two different
> keyspaces connected to the same node.
> The prepared statements uses the keyspace that was set while the statement
> was perpared (public final CFDefinition cfDef).
> When reusing the Statement only the cql-query is used to create a key and the
> keyspace is ignored. When the same query is prepared and used for two
> different Keyspaces the wrong keyspace can be used.
> The fix is not to ignore the keyspace when reusing the statement.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
