Hi Binti, Can you please properly subscribe to the mailing list so that the community can receive email notifications? Here is the instruction: http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1
bintisepaha wrote > We have a use case where multiple database tables/caches need to updated > within a transaction, on the cluster side I can achieve this using > IgniteTransactions. But I want to do the same while its going to the DB > Store using write-behind. Seems like CacheStoreSession is something I > should be using, but I could not find examples that wrote to 2 tables > together in a transaction. Does ignite have some way to chain this when > writing to the database or does this have to be a custom cacheStore > implementation? > > table A -> cache A > table B -> cache B > > But when A is updated, B is always updated (ignite transaction). How can > write-behind achieve this? This is possible only with write-through with the help of cache store session listeners. See store example [1] on how it is used. With write-behind database is updated asynchronously, so the DB updates are independent and can't be enlisted in a single DB transaction. [1] https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/datagrid/store/jdbc/CacheJdbcStoreExample.java -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Database-transaction-updating-more-than-1-table-from-CacheStore-tp4197p4202.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.