Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CA+eZwrHO1ivV9JBFYOpo55RmCWizTzZ8XrgaU7PydEtkiFBgXQ@mail.gmail.com>
References: 
 <CAKoNANuGucJnksGJQtjkX+8RyAJ6M8NJc16e_+=xvnq6x1RPHA@mail.gmail.com>
 <CA+eZwrHO1ivV9JBFYOpo55RmCWizTzZ8XrgaU7PydEtkiFBgXQ@mail.gmail.com>
From: Raul Kripalani <raulk@apache.org>
Date: Thu, 22 Oct 2015 13:35:01 +0100
Message-ID: 
 <CAKoNANvG5FFzPs6k0HHRf64E1pgC+TR+D7hT0p2CSoyHCcOmxg@mail.gmail.com>
Subject: Re: Data Snapshots in Ignite
To: dev@ignite.apache.org
Content-Type: multipart/alternative; boundary=001a113f203074ddf30522b0ba1a

--001a113f203074ddf30522b0ba1a
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hey Sergey,

I like your idea of Autocloseable snapshots!

Regards,

*Ra=C3=BAl Kripalani*
PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and
Messaging Engineer
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk

On Wed, Oct 21, 2015 at 1:51 PM, Sergi Vladykin <sergi.vladykin@gmail.com>
wrote:

> Raul,
>
> Actually SQL indexes are already snapshotable. I'm not sure if it does ma=
ke
> sense to make
> the whole cache (with full cache API support) snapshotable, but I like yo=
ur
> idea
> about running multiple SQL statements against the same snapshot.
>
> Also I don't think that it is a good idea to keep snapshots for a long
> time,
> so I'd prefer to have typical AutoClosable API like:
>
> try (Snapshot s =3D ...) {
>     s.query(...);
>     s.query(...);
>     s.query(...);
> }
>
> Though I'm not sure when we will be able to get down to this.
>
> Sergi
>
> 2015-10-21 12:06 GMT+03:00 Raul Kripalani <raulk@apache.org>:
>
> > Hey guys,
> >
> > LevelDb has a functionality called Snapshots which provides a consisten=
t
> > read-only view of the DB at a given point in time, against which querie=
s
> > can be executed.
> >
> > To my knowledge, this functionality doesn't exist in the world of open
> > source In-Memory Computing. Ignite could be an innovator here.
> >
> > Ignite Snapshots would allow queries, distributed closures, map-reduce
> > jobs, etc. It could be useful for Spark RDDs to avoid data shift while
> the
> > computation is taking place (not sure if there's already some form of
> > snapshotting, though). Same for IGFS.
> >
> > Example usage:
> >
> >     IgniteCacheSnapshot snapshot =3D
> > ignite.cache("mycache").snapshots().create();
> >
> >     // all three queries are executed against a view of the cache at th=
e
> > point in time where it was snapshotted
> >     snapshot.query("select ...");
> >     snapshot.query("select ...");
> >     snapshot.query("select ...");
> >
> > In fact, it would be awesome to be able to logically save this snapshot
> > with a name so that later jobs, queries, etc. can run on top of it, e.g=
.:
> >
> >     IgniteCacheSnapshot snapshot =3D
> > ignite.cache("mycache").snapshots().create("abc");
> >
> >     // ...
> >     // in another module of a distributed system, or in another thread =
in
> > parallel, use the saved snapshot
> >     IgniteCacheSnapshot snapshot =3D
> > ignite.cache("mycache").snapshots().get("abc");
> >     ....
> >
> > Named snapshotting can be dangerous due to data retention, e.g. imagine
> > keeping a snapshot for 2 weeks! So we should force the user to specify =
a
> > TTL:
> >
> >     IgniteCacheSnapshot snapshot =3D
> > ignite.cache("mycache").snapshots().create("abc", 2, TimeUnit.HOURS);
> >
> > Such functionality would allow for "reporting checkpoints" and "time
> > travel", for example, where you want users to be able to query the data
> as
> > it stood 1 hour ago, 2 hours ago, etc.
> >
> > What do you think?
> >
> > P.S.: We do have some form of snapshotting in the Compute checkpointing
> > functionality =E2=80=93 but my proposal is to generalise the notion.
> >
> > Regards,
> >
> > *Ra=C3=BAl Kripalani*
> > PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data a=
nd
> > Messaging Engineer
> > http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalan=
i
> > http://blog.raulkr.net | twitter: @raulvk
> >
>

--001a113f203074ddf30522b0ba1a--