You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by Andrey Mashenkov <am...@gridgain.com> on 2017/06/19 12:39:59 UTC
Fwd: Transaction Boundary - Data Streamer
Crossposting to dev.
Igniters,
Would someone please update documentation that IgniteDataStreamer is not
designed to be used inside transactions?
---------- Forwarded message ----------
From: Andrey Mashenkov <am...@gridgain.com>
Date: Mon, Jun 19, 2017 at 3:37 PM
Subject: Re: Transaction Boundary - Data Streamer
To: user@ignite.apache.org
Hi Ganesh,
This will not work. IgniteDataStreamer is not transactional by design.
On Thu, Jun 15, 2017 at 10:37 AM, Sri Ganesh V <vs...@yahoo.co.in>
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.
>
Re: Transaction Boundary - Data Streamer
Posted by Yakov Zhdanov <yz...@apache.org>.
Done. Revision hash ec9d47b197738459b7721d5b393f5be223cd76e0
--Yakov