Luqman, You can try EntryProcessor API - invoke the processor passing an entry key and a new value as parameters. When the processor is executed on the cluster side, Ignite will give you the old value and the new one passed by you. Compare them and decide which to store in the cache.
CacheEntryProcessorExample demonstrates the basics of EntryProcessor APIs. -- Denis On Wed, Aug 29, 2018 at 4:08 PM luqmanahmad <[email protected]> wrote: > Thanks Denis for getting back to me much appreciated. > > The use case we have is we have millions of data points which is updated by > the other teams in separate databases. Whenever this happens we receive a > message upon update and it triggers the load cache process in ignite. > > Until now we did not have any problem but now we have certain requirements > in which we have to do some calculation based on some fields from cache > value and decide whether to update the value inside the cache or not. Maybe > I am not thinking straight over here, but is there something I am missing > from ignite which can be used to overcome this problem. > > Thanks, > Luqman > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
