Re: Alternative Pub Sub mechanism between Operators

A service provider interface and factory mechanism can be used to swap out the entire implementation, but more likely to customize some aspects of the implementation (security etc.). On Mon, Sep 14, 2015 at 11:35 PM, Yogi Devendra wrote: > Can we say that proposed module interface can be impleme

Re: Sequencing of operator calls

It has not changed the operator execution model. State serialization is still synchronous, write to HDFS is taken out of the operator thread. On Tue, Sep 15, 2015 at 8:18 AM, Amol Kekre wrote: > > Sent too soon. Has asynchronous checkpointing changed this? > > Amol > > Sent from my iPhone > > >

Re: Sequencing of operator calls

Sent too soon. Has asynchronous checkpointing changed this? Amol Sent from my iPhone > On Sep 15, 2015, at 12:38 AM, Bhupesh Chawda wrote: > > Hi All, > > Is it safe to assume that the checkpointed() and the beginWindow() calls > are sequenced? > In other words, are these calls part of the s

Re: Sequencing of operator calls

Apex guarantees single thread execution. The answer should be yes Amol Sent from my iPhone > On Sep 15, 2015, at 12:38 AM, Bhupesh Chawda wrote: > > Hi All, > > Is it safe to assume that the checkpointed() and the beginWindow() calls > are sequenced? > In other words, are these calls part of

Sequencing of operator calls

Hi All, Is it safe to assume that the checkpointed() and the beginWindow() calls are sequenced? In other words, are these calls part of the same thread and may not run in parallel? Thanks. -- -Bhupesh