Not sure how CQEngine will help for snapshotting of Ignite. Can you explain?
On Wed, Oct 21, 2015 at 7:48 PM, Alexey Kuznetsov <akuznet...@gridgain.com> wrote: > Some time ago we already discussed snapshots idea while discussing library > "cqengine" [1]. > > May be this library could be useful in snapshot mode. > > [1] Sources: https://github.com/npgall/cqengine > Docs: https://code.google.com/p/cqengine/ > > On Thu, Oct 22, 2015 at 8:48 AM, Konstantin Boudnik <c...@apache.org> > wrote: > > > On Wed, Oct 21, 2015 at 05:58PM, Dmitriy Setrakyan wrote: > > > On Wed, Oct 21, 2015 at 4:48 PM, Konstantin Boudnik <c...@apache.org> > > wrote: > > > > > > > I like it quite a bit, as well! Ticket would make the most sense as > > well, > > > > so > > > > there will be a single place to collect the design docs (if needed), > > etc. > > > > > > > > On Wed, Oct 21, 2015 at 04:45PM, Dmitriy Setrakyan wrote: > > > > > I also really like the idea. One potential use case is fraud > > analysis in > > > > > financial institutions. Rarely it makes sense to perform such > > analysis > > > > on a > > > > > life system, but rather a snapshot of some data needs to be taken > and > > > > > analyzed offline. > > > > > > > > > > I think snapshots should be saved to disk, so users could load them > > for > > > > > analysis on a totally different cluster. > > > > > > > > I think disk persistence should be optional, not mandatory. > > > > > > > > > > I would actually prefer to support disk-only snapshots. I think it will > > be > > > difficult (double-the-work) to support both, in-memory and disk > formats. > > > Also, storing snapshots in-memory would require extra memory (a lot of > > it) > > > for something that gets saved mainly for historic purposes or offline > > > analysis. > > > > Ah, good points! Agree. > > > > > > > -- > Alexey Kuznetsov > GridGain Systems > www.gridgain.com >
