Re: Migrating From Hazelcast Service Interface To Apache Ignite Service Interface

will be appending to via an insert as well as separate dictionaries to make sense of the binary blobs during queries. thanks, Gareth On Tue, Feb 16, 2016 at 4:07 PM, vkulichenko [via Apache Ignite Users] <ml-node+s70518n3045...@n6.nabble.com> wrote: > Hi Gareth, > > gcollins

Re: Migrating From Hazelcast Service Interface To Apache Ignite Service Interface

Can you point me an example of what you are suggesting? Or suggest what classes I should look at as an entry point? thanks in advance, Gareth On Tue, Feb 16, 2016 at 6:43 PM, dsetrakyan [via Apache Ignite Users] wrote: > > > On Tue, Feb 16, 2016 at 12:00

Re: Migrating From Hazelcast Service Interface To Apache Ignite Service Interface

Hi Val, Thanks again for the response! I guess the SpiQuery can help me part of the way potentially, but it doesn't give me the control to manage internal memory structure, replication, custom persistence etc. The Hazelcast API I am referring to is described in chapter 24 of the Hazelcast

Re: Migrating From Hazelcast Service Interface To Apache Ignite Service Interface

Thanks very much for the responses! Those are all important features of Ignite, and I believe these features are one of the big reasons why we are wanting to move away from Hazelcast (in Hazelcast, if you wanted to deploy different services to different sets of nodes you need to set up different