[GitHub] ignite pull request: Ignite-2710: Proper invalidation of session w...

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

[GitHub] ignite pull request: Ignite-2710: Proper invalidation of session w...

andrey-kuznetsov
GitHub user shroman opened a pull request:

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

    Ignite-2710: Proper invalidation of session within a request.

   

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

    $ git pull https://github.com/shroman/ignite ignite-2710

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

    https://github.com/apache/ignite/pull/530.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 #530
   
----
commit 827d7ff5ce08c70e3980910b02310d840c341976
Author: shtykh_roman <[hidden email]>
Date:   2016-03-01T09:22:55Z

    IGNITE-2710: Proper invalidation of session within a request.

commit 828fa8c7b73750b247316ef0d668cd4cb49df410
Author: shtykh_roman <[hidden email]>
Date:   2016-03-01T09:58:42Z

    IGNITE-2710: Proper invalidation of session within a request. Disabled testInvalidatedSession for transactional cache.

----


---
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: Ignite-2710: Proper invalidation of session w...

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

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


---
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.
---