Something like a Spring TransactionSynchornizationmanager. But using that will not work, because it workds for the current node, and Ignite can choose to do the final commit in other JVMs.
My problem is that I have 4 caches with Write Through. They use Spring Transactions to do JDBC updates/inserts. However if the transaction gets committed from other node, each write to JDBC creates a new Transaction as no transaction exists when it gets called. Is there any way to initiate a transaction before Ignite calls the write behind stores so that all existing calls have a transaction and do not create their own. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Pre-Hook-before-actual-Ignite-commit-tp5679p5685.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
