ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From vkulichenko <valentin.kuliche...@gmail.com>
Subject Re: Database transaction updating more than 1 table from CacheStore
Date Tue, 19 Apr 2016 21:02:06 GMT

Session listener is just a callback that is called before and after cache
transaction. In case of write-through you can use it to start and
commit/rollback DB transaction along with cache transaction. With
write-behind it doesn't help much because in this case DB is updated from
primary nodes and generally there are several of them in one transaction,
which makes maintaining a single DB transaction impossible. The only way to
fully guarantee transactional consistency is using write-through.


View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Database-transaction-updating-more-than-1-table-from-CacheStore-tp4197p4344.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

View raw message