[jira] [Commented] (IGNITE-5291) SQL: plans cache does not clear on cache stop

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-5291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16024868#comment-16024868 ] 

ASF GitHub Bot commented on IGNITE-5291:
----------------------------------------

GitHub user alexpaschenko opened a pull request:

    https://github.com/apache/ignite/pull/2008

    IGNITE-5291 Correct handling of cache stop in IgniteH2Indexing

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-5291

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/2008.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 #2008
    
----
commit de522ebcc27807f4316b18349f5024f28f1bcf2b
Author: Alexander Paschenko <al...@gmail.com>
Date:   2017-05-25T15:21:13Z

    IGNITE-5291 Correct handling of cache stop in IgniteH2Indexing

----


> SQL: plans cache does not clear on cache stop
> ---------------------------------------------
>
>                 Key: IGNITE-5291
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5291
>             Project: Ignite
>          Issue Type: Bug
>          Components: sql
>    Affects Versions: 2.0
>         Environment: After cache-schema decoupling mutation of {{DmlStatementsProcessor#planCache}} appears to be broken (different pieces of code contexts operate different schema names), have to do this consistently.
>            Reporter: Alexander Paschenko
>            Assignee: Alexander Paschenko
>             Fix For: 2.1
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)