Hi, To force Ignite to reload value from CacheStore it's enough to remove corresponding key. Commit changes to database and remove corresponding keys, what should do the job.
But the better and more reliable way would be in my opition to do all writes to store using only Ignite. 2016-07-07 13:49 GMT+03:00 pragmaticbigdata <[email protected]>: > We are using ignite version 1.6. Our cache is configured as write through > for > data consistency reasons. What are the different ways to update the ignite > cache when the rdbms store is updated by other applications? > One option would be write a hook that calls the data load api's of ignite > (CacheStore or IgniteDataStreamer ?) to update the ignite cache. In this > case would ignite again try to update the rdbms store since the cache is > configured for write through? If so, is there a way to avoid it? > > Thanks > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Handling-external-updates-to-persistence-store-tp6143.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > -- Best regards, Alexei Scherbakov
