If you need transactional in your operations, you can use optimistic&serializable transactions by implementing and registering a receiver into your datastreamer as explained here
https://apacheignite.readme.io/docs/transactions#deadlock-free-transactions and for datastreamer here https://apacheignite.readme.io/docs/data-streamers#streamreceiver On Mon, Jun 19, 2017 at 2:37 PM, Andrey Mashenkov <[email protected]> wrote: > Hi Ganesh, > > This will not work. IgniteDataStreamer is not transactional by design. > > > > On Thu, Jun 15, 2017 at 10:37 AM, Sri Ganesh V <[email protected]> > wrote: > >> Hi, >> >> Is it possible to use streamers to add data to different transactional >> caches with transaction boundary defined? >> >> Example : >> Transaction tx = ignite.transactions().txStart(); >> >> strmr1.addData(1,"xyz"); // strmr1 is configured to stream data >> to cache1 (cache1-transactional) >> strmr2.addData(2,"abc"); // strmr2 is configured to stream data >> to cache2 (cache2-transactional) >> >> tx.commit(); >> >> Please suggest the best way to achieve this with optimal performance for >> both cache inserts and updates. >> >> Thanks, >> Ganesh >> >> >> >> -- >> View this message in context: http://apache-ignite-users.705 >> 18.x6.nabble.com/Transaction-Boundary-Data-Streamer-tp13803.html >> Sent from the Apache Ignite Users mailing list archive at Nabble.com. >> > >
