Fatih, Can you give more details about the use case addressed by this implementation?
-Val On Tue, Jun 27, 2017 at 3:45 PM, Denis Magda <dma...@apache.org> wrote: > Faith, > > Thanks for sharing it with us. > > In general, we can always wrap this code up in a form of an example to be > delivered with every Ignite release. > > But probably it makes sense to add it to the core streaming functionality. > *Igniters*, what’d you think? > > — > Denis > > > On Jun 27, 2017, at 12:29 AM, fatih <fatih.teki...@gmail.com> wrote: > > > > Hi > > > > We have implemented some receivers to be able to update data in data > nodes > > by ignite datastreamer api. > > > > There is an associated ticket as below already exist. We thought it > would be > > useful to use that implementation from ignite directly. Maybe can be > added > > to ignite directly. > > > > http://apache-ignite-users.70518.x6.nabble.com/ > Transaction-Boundary-Data-Streamer-td13803.html#a14078 > > AbstractTransactionalStreamReceiver.java > > <http://apache-ignite-developers.2346864.n4.nabble.com/file/n19129/ > AbstractTransactionalStreamReceiver.java> > > > > TimestampBasedUpdateStreamReceiver.java > > <http://apache-ignite-developers.2346864.n4.nabble.com/file/n19129/ > TimestampBasedUpdateStreamReceiver.java> > > > > > > > > > > -- > > View this message in context: http://apache-ignite- > developers.2346864.n4.nabble.com/DataStreamer-Transactional-and-Timestamp- > Implementation-tp19129.html > > Sent from the Apache Ignite Developers mailing list archive at > Nabble.com. > >
