It turns out that the flush process is executed when there are "n+1" rows that change. If I set writeBehindFlushSize = 2, then the writing process will be executed on the third change in the table because "with the write-behind approach, only the last update to an entry will be written to the underlying storage" [1].
I hope that I get it right. Thanks. [1] https://apacheignite.readme.io/docs/persistent-store#section-write-behind-caching ----- -- Ricky -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Write-behind-Flush-Size-tp12336p12367.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
