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] <[email protected]> wrote: > > > On Tue, Feb 16, 2016 at 12:00 PM, collins <[hidden email]> wrote: > >> 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 Manual (Extending Hazelcast - User Defined Services). This >> API was added when they released Hazelcast 3.0. As part of this >> release, they also rewrote all their internal data structures (e.g. >> Map, Queue etc) to use this same API so that you can write a service >> that can do anything their internal data structures can do. > > > Hm… I am not sure I fully understand. Why not just create caches or data > structures internally within Ignite service and make use of them in your > service logic? What am I missing? > > D. > > > ________________________________ > If you reply to this email, your message will be added to the discussion > below: > http://apache-ignite-users.70518.x6.nabble.com/Migrating-From-Hazelcast-Service-Interface-To-Apache-Ignite-Service-Interface-tp2970p3048.html > To unsubscribe from Migrating From Hazelcast Service Interface To Apache > Ignite Service Interface, click here. > NAML -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Migrating-From-Hazelcast-Service-Interface-To-Apache-Ignite-Service-Interface-tp2970p5811.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
