[
https://issues.apache.org/jira/browse/IGNITE-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14975530#comment-14975530
]
Dmitriy Setrakyan commented on IGNITE-1789:
-------------------------------------------
I still think we should snapshot to disk and preserve a snapshot on disk. This
would make everything else, like frozen state possible. For example, user can
snapshot to disk, then load from disk into a different cache and perform any
kind of Ignite operation there, like so:
{code}
cache.saveSnapshot("mySnapshot"); // Should be sync or async mode.
IgniteCache<a, b> otherCache = ignite.getOrCreateCache("otherCache");
otherCache.loadSnapshot("mySnapshot");
{code}
> Data Snapshots for Ignite caches
> --------------------------------
>
> Key: IGNITE-1789
> URL: https://issues.apache.org/jira/browse/IGNITE-1789
> Project: Ignite
> Issue Type: New Feature
> Components: cache
> Reporter: Raúl Kripalani
>
> There was a discussion in the dev forum about Data Snapshots in Ignite as a
> way to obtain a consistent and "frozen" view of one or multiple caches in
> order to execute a set of SQL queries, distributed closures, map reduce, etc.
> without having to worry about data slippage (or moving data).
> The discussion is here:
> http://apache-ignite-developers.2346864.n4.nabble.com/Data-Snapshots-in-Ignite-td4183.html
> and we still need to mature the idea, but several users chimed in and
> considered it interesting.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
