You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Michael Griggs (JIRA)" <ji...@apache.org> on 2015/12/09 15:12:10 UTC

[jira] [Commented] (IGNITE-1789) Data Snapshots for Ignite caches

    [ https://issues.apache.org/jira/browse/IGNITE-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15048717#comment-15048717 ] 

Michael Griggs commented on IGNITE-1789:
----------------------------------------

For my use-case, I would prefer to have the option to copy all in-memory objects and give them new keys that have the snapshot name added in some way, but remain in the same cache.  So for example, Country:GB would get snapshotted and copied to Country:GB:snapshot1.0, and both Country:GB and Country:GB:snapshot1.0 would be stored in memory.

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