[
https://issues.apache.org/jira/browse/IGNITE-6637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16205813#comment-16205813
]
ASF GitHub Bot commented on IGNITE-6637:
----------------------------------------
GitHub user alexpaschenko opened a pull request:
https://github.com/apache/ignite/pull/2860
IGNITE-6637 Statements cache clear on cache destroy.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6637
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2860.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2860
----
commit 0f2acd36c851a4f4ebdf5eff976e94289aa09bf2
Author: Alexander Paschenko <[email protected]>
Date: 2017-10-16T12:18:46Z
IGNITE-6637 Statements cache clear on cache destroy.
----
> No proper cleanup of statements cache is done on table drop
> -----------------------------------------------------------
>
> Key: IGNITE-6637
> URL: https://issues.apache.org/jira/browse/IGNITE-6637
> Project: Ignite
> Issue Type: Bug
> Security Level: Public(Viewable by anyone)
> Components: sql
> Reporter: Alexander Paschenko
> Assignee: Alexander Paschenko
> Fix For: 2.3
>
> Attachments: IgniteCacheLocalQuerySelfTest.java
>
>
> We should cleanup statements cache whenever cache is deregistered - otherwise
> it's possible to retrieve from statements cache a statement that is prepared
> from H2 perspective but may not be executed. Such situation may arise for any
> dynamic cache, not only for that created via SQL.
> Reproducer attached.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
