Hi,
Yes I think you can manually store the latest watermark by using the
OperatorStateStore that you get if your user function implements the
CheckpointedFunction interface.
Best,
Aljoscha
> On 30. May 2017, at 13:43, rhashmi wrote:
>
> Thanks Aljoscha Krettek,
>
> So the results will not be
Thanks Aljoscha Krettek,
So the results will not be deterministic for late events. For idempotent
update, i would need to find an additional key base of current event time if
they are late and attached to the aggregator which probably possible by
doing some function(maxEventTime, actualEventTime)
Hi,
If you use tumbling windows or sliding windows then Flink will not keep
additional meta data besides the actual window contents. Also, if you use a
Trigger that purges when firing Flink will clean the window contents after
firing a window. This means that you can set allowed lateness to MAX
Could you elaborate this more? If i assume if i set window time to max ..
does it mean my window will stay for infinite time framework,
Wouldn't this may hit memory overflow with time?
--
View this message in context:
http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/State-i
Hi,
Why don’t you set the allowed lateness to Long.MAX_VALUE? This way no data will
ever be considered late. If you make the trigger via
PurgingTrigger.of(EventTimeTrigger.of(…)). You ensure that window state is not
kept after a window fires.
Best,
Aljoscha
> On 17. May 2017, at 13:39, rizhas
Yes .. is there any possibility access flink state variables in
WindowAssigner.assignWindows method?
--
View this message in context:
http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/State-in-Custom-Tumble-Window-Class-tp13177p13196.html
Sent from the Apache Flink User Maili
Thanks Walther,
I am not keeping my window forever.if the event is arrived after graced
period(lateness) i update event time to current time or say last event time.
That essentially solve infinite issue.
1.3 is not stable yet?
--
View this message in context:
http://apache-flink-user-maili
Hi,
in general, a class level variable is not managed by Flink if it is not
defined as state or the function does not implemented ListCheckpointed
interface. Allowing infinite lateness also means that your window
content has to be stored infinitely. I'm not sure if I understand your
implement
