Hi Andrew, Thank you for the response. 1. yes, I will try this way to build sub caches 2. yes, make sense. 3. I tested EvictionPolicy, it seemed to be not available in ignite 2.0+, please refer to my earlier discuss (with denis) <http://apache-ignite-users.70518.x6.nabble.com/SortedEvictionPolicy-doesn-t-work-as-expected-td20249.html#a20269> , is there sth else that I need to know?
I'm fighting against none-blocking real-time processes, I hope I could have better understanding of ignite documents Andrew Mashenkov wrote > Hi, > > 1. NodeFilter can be used [1] to bound cache to certain data nodes. > 2. You can subscribe to cache updates via ContinuousQuery [2]. > But keep in mind, ContinuousQuery listener is called from sensitive code > and it is usually bad idea to make blocking operations in it. > 3. To keep only TOP N entries in cache, a EvictionPolicy [3] can be used. > EvictionPolicy doesn't support persistence. > > Hope, this helps. > > [1] > https://stackoverflow.com/questions/39612201/apache-ignite-how-to-deploy-cache-to-some-certain-cluster-group > [2] https://apacheignite.readme.io/docs/continuous-queries > [3] > https://apacheignite.readme.io/docs/evictions#section-first-in-first-out-fifo- > > On Thu, Mar 29, 2018 at 2:42 AM, vkulichenko < > valentin.kulichenko@ > > > wrote: > >> Sorry, I'm still failing to understand what you're trying to achieve. >> What >> is >> the reason to manually maintain a tree structure which is basically an >> index? Why not use Ignite indexes that are provided out of the box? >> >> -Val >> >> >> >> -- >> Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >> > > > > -- > Best regards, > Andrey V. Mashenkov -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
