Description
Currently if there are several updates for the same key, write behind store will write only one of them within a single batch. I.e. second update will override the first one if the latter is not written to DB yet.
This is good from performance and memory consumption standpoint, however sometimes it's required to write all updates that happen in cache.
We can add parameter to CacheConfiguration that will switch this behavior and implement it in GridCacheWriteBehindStore. Default behavior should remain the same.
Attachments
Issue Links
- duplicates
-
IGNITE-4927 Write behind - add an option to skip write coalescing
- Closed