Re: Cache.getAll can return partially commited results. IGNITE-4809

Ah, ok thanks for clarifying. I will leave my ticket unassigned ср, 31 мая 2017 г. в 21:10, Alexey Goncharuk : > Aleksey, > > Generally, this decision cannot be made on a single node because a > transaction may affect multiple nodes, and one node may have already >

Re: Cache.getAll can return partially commited results. IGNITE-4809

Aleksey, Generally, this decision cannot be made on a single node because a transaction may affect multiple nodes, and one node may have already committed the transaction and the other - not. There is a dependant ticket in the ticket you are currently working on which will cover all the caes.

Re: Cache.getAll can return partially commited results. IGNITE-4809

one possible solution is to lock entry reading section while userCommit() method is executing. ср, 31 мая 2017 г., 16:52 ALEKSEY KUZNETSOV : > Hi, Igntrs! > When the first writer thread has commited values and cache entries are > getting updated with this new values,

Cache.getAll can return partially commited results. IGNITE-4809

Hi, Igntrs! When the first writer thread has commited values and cache entries are getting updated with this new values, another thread is getting partially assigned values through the cache.getAll(keys) should this method wait for all newly updated entries to finish , or should it throw the