Hi Greg, If I'm an Ignite committer it doesn't mean that my curiosity is driven by a kind of marketing needs :) Moreover, Ignite community doesn't provide any kind of comparison sheets or whatever.
So, returning back to my original question. I had to deal with this use case many times in practice. And all they time I had to preload all the data from a persistence in memory if I wanted to execute SQL or other kind of non key based queries right away. Ignite, Hazelcast and many other platforms I know doesn't support such a feature. But looks like at least Geode can now deal with this use case according to the text on the main page (Object Query Language allows distributed query execution on hot and *cold* data, with SQL-like capabilities, including joins.). Is it so, guys? - Denis On Fri, Aug 19, 2016 at 12:08 PM, Greg Chase <gch...@gmail.com> wrote: > Hi Denis, > How does Ignite handle this use case? > > I trust you are fishing for comparisons. > > Greg > > This email encrypted by tiny buttons & fat thumbs, beta voice recognition, > and autocorrect on my iPhone. > > On Aug 19, 2016, at 11:59 AM, Denis Magda <magda7...@gmail.com> wrote: > > Hello Geode community, > > I've been investigating possibilities of Geode Persistence for a while and > still can't get it clear whether I need to have all my data in memory if I > want to execute OQL queries or OQL engine works over the persistence as > well. > > My use case is the following. During the cluster startup I don't want to > wait while all the data has been pre-loaded from the persistence to RAM and > want to execute OQL queries right away. Is it feasible to implement with > Geode? Please provide me with the links where I can read more about this. > > Regards, > Denis > > -- Удачи, Денис Магда
