On Sat, Jul 9, 2022 at 9:28 AM Reuven Lax via user
wrote:
>
>
> On Fri, Jul 8, 2022 at 1:37 PM gaurav mishra
> wrote:
>
>> Maybe the previous post was too verbose so I will try to summarize my
>> question -
>> If one instance of DoFn tries to set a timer for a time which is behind
>> the pipelin
On Fri, Jul 8, 2022 at 1:37 PM gaurav mishra
wrote:
> Maybe the previous post was too verbose so I will try to summarize my
> question -
> If one instance of DoFn tries to set a timer for a time which is behind
> the pipeline's watermark, can this cause the pipeline to stall for other
> keys as w
Maybe the previous post was too verbose so I will try to summarize my
question -
If one instance of DoFn tries to set a timer for a time which is behind the
pipeline's watermark, can this cause the pipeline to stall for other keys
as well?
"stall" meaning here - other keys' timers will start laggin
Hello,
I have a pipeline which is generating heartbeats using looping timers in a
stateful dofn. Following is pseudo code for the process element and onTimer
methods
StateSpec> lastSeenMsg = StateSpecs.value(...);
TimerSpec loopingTimer = TimerSpecs.timer(TimeDomain.EVENT_TIME);
processElemnt(in
