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
implementation correctly, but overriding classes that where not intended
for overriding seems not to be a good solution. With Flink 1.3 there
will be side outputs that allow to retrieve all late data as a stream
for not losing elements at all: WindowedStream#sideOutputLateData, maybe
this might be an option for you.
Hope that helps.
Timo
Am 16.05.17 um 23:25 schrieb rizhashmi:
i have requirement not to reject events .. even if they are late(after
maximum allowedness). So the way i achieve this but overriding Tumbling
window class and update event time to last event time if the event is late
and for identification attached additional column in db as
(currentevent/msPerHour - eventtime/msPerHour)
currentevent is a class level variable in Tumbling window.
My problem statement is, in case of full runtime crash, can flink recover
tumblewindow state?
if yes how?
--
View this message in context:
http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/State-in-Custom-Tumble-Window-Class-tp13177.html
Sent from the Apache Flink User Mailing List archive. mailing list archive at
Nabble.com.
