Atri, What is the use case you have in mind? If you are thinking about rolling back a transaction if some operations fail during processing that can be achieved within the current paradigm.
Thanks On Fri, Aug 28, 2015 at 2:14 PM, Chetan Narsude <[email protected]> wrote: > Atri, > > BEGIN_WINDOW, and END_WINDOW control events demarcate the the > transaction. We do not hold the first event after BEGIN_WINDOW hostage > until the END_WINDOW is received. This allows us to provide almost zero > latency at per tuple level. This is one of the the differentiating > paradigms for Apex. > > If we do it otherwise - the platform degrades to micro-batch processing > mode. More details about it here: > > > https://www.datatorrent.com/real-time-event-stream-processing-what-are-your-choices/ > > > Let me know if this answers your question or I misunderstood the question. > > -- > Chetan > > > > On Fri, Aug 28, 2015 at 1:37 PM, Atri Sharma <[email protected]> wrote: > > > Team, > > > > Does it make sense to have functionality to have all or nothing > > transactional system for windows? With future functionality to have > dynamic > > operators I feel it makes sense to allow data from an entire window to be > > processed or none of the data to be sent. > > > > I am not sure if window batching in its current form is a logical > > implementation of this feature. > > > > Thoughts? > > > > Regards, > > > > Atri > > >
