[
https://issues.apache.org/jira/browse/IGNITE-6030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16158603#comment-16158603
]
ASF GitHub Bot commented on IGNITE-6030:
----------------------------------------
GitHub user kdudkov opened a pull request:
https://github.com/apache/ignite/pull/2624
IGNITE-6030 Persistence per memoryPolicy (first working test)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6030
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2624.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 #2624
----
commit 6c593ff23613e53155f51f49acda49e5a01d9178
Author: Konstantin Dudkov <[email protected]>
Date: 2017-09-08T13:00:57Z
IGNITE-6030 Persistence per memoryPolicy (first working test)
----
> Allow enabling persistence per-cache
> ------------------------------------
>
> Key: IGNITE-6030
> URL: https://issues.apache.org/jira/browse/IGNITE-6030
> Project: Ignite
> Issue Type: New Feature
> Components: persistence
> Affects Versions: 2.1
> Reporter: Alexey Goncharuk
> Assignee: Konstantin Dudkov
> Fix For: 2.3
>
>
> Also, when cache native persistence is disabled, we need to make sure that
> different {{CacheStores}} can be configured on per-cache basis.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
