Nice, that might work - thanks Denis
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
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
If you use a cache store, and change values in the underlying database,
then they won't be propagated to Ignite, and old values will be used.
There is no mechanism, that can notify the cache about updates on the
3rd-party DB.
But if you didn't have this value in the cache, and read-through
anyone from anyone would be highly appreciated
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi,
Is there any feature in ignite through which I can decide whether to keep
the old value or new value in a cache? We have few cases when the update
comes from the persistence store we want do not want to update the cache
value and want to keep the old one.
Thanks,
Luqman
--
Sent from:
