[
https://issues.apache.org/jira/browse/IGNITE-6853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16326691#comment-16326691
]
Jason Man commented on IGNITE-6853:
-----------------------------------
It's difficult to simulate the Cassandra errors without using a mocking
framework. I think this is why currently there is a lack of 'negative' tests
covering the ignite-cassandra module, and why this bug was not discovered/fixed
earlier.
Perhaps we could start discussing this in the community dev email list?
> Cassandra cache store does not clean prepared statements cache when remove
> old cassandra session
> ------------------------------------------------------------------------------------------------
>
> Key: IGNITE-6853
> URL: https://issues.apache.org/jira/browse/IGNITE-6853
> Project: Ignite
> Issue Type: Bug
> Components: cassandra
> Affects Versions: 2.3
> Reporter: Mikhail Cherkasov
> Assignee: Jason Man
> Priority: Major
> Labels: important
> Fix For: 2.4
>
>
> Cassandra cache store does not clean prepared statements cache when remove
> old cassandra session which can lead to:
> Prepared
> statement cluster error detected, refreshing Cassandra session
> com.datastax.driver.core.exceptions.InvalidQueryException: Tried to execute
> unknown prepared query : 0xcad5832309a512feeb602eec67408130. You may have
> used a PreparedStatement that was created with another Cluster instance.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
