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/
