[GitHub] ignite pull request #827: IGNITE-3340 .NET: Fix cache store release on cache...

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[GitHub] ignite pull request #827: IGNITE-3340 .NET: Fix cache store release on cache...

andrey-kuznetsov
GitHub user ptupitsyn opened a pull request:

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

    IGNITE-3340 .NET: Fix cache store release on cache destroy

   

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

    $ git pull https://github.com/ptupitsyn/ignite ignite-3340

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

    https://github.com/apache/ignite/pull/827.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 #827
   
----
commit c40ee2d4381a4eea01978edc5f2999b7a632d74f
Author: Pavel Tupitsyn <[hidden email]>
Date:   2016-06-23T14:40:52Z

    IGNITE-3340 .NET: Cache store is not destroyed on DestroyCache - wip

commit 9ed1b033168ffa69f0766e080238e231a4971135
Author: Pavel Tupitsyn <[hidden email]>
Date:   2016-06-23T14:55:25Z

    wip

commit 019ddfc438c80153fe6ac4c1d7f68b8a6b7721f0
Author: Pavel Tupitsyn <[hidden email]>
Date:   2016-06-23T15:07:38Z

    Add handle test

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.
---
Reply | Threaded
Open this post in threaded view
|

[GitHub] ignite pull request #827: IGNITE-3340 .NET: Fix cache store release on cache...

andrey-kuznetsov
Github user ptupitsyn closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [hidden email] or file a JIRA ticket
with INFRA.
---