[GitHub] ignite pull request #2127: GNITE-5484 DataStructuresCacheKey and DataStructu...

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

[GitHub] ignite pull request #2127: GNITE-5484 DataStructuresCacheKey and DataStructu...

andrey-kuznetsov
GitHub user mcherkasov opened a pull request:

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

    GNITE-5484 DataStructuresCacheKey and DataStructureInfoKey should have GridCacheInternal marker

   

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

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

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

    https://github.com/apache/ignite/pull/2127.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 #2127
   
----
commit e5ad1aaada0d053a2507bfe6192551f216f28247
Author: mcherkasov <[hidden email]>
Date:   2017-06-14T11:32:45Z

    Added GridCacheInternal marker for DataStructureInfoKey and DataStructuresCacheKey.

commit 4f93e8d1a0ba1f6de0158d3b945b6a3838399121
Author: mcherkasov <[hidden email]>
Date:   2017-06-14T11:33:05Z

    Added test to check that DataStructures can't be evicted.

----


---
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 #2127: IGNITE-5484 DataStructuresCacheKey and DataStruct...

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

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


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