You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have quoted the following paragraphs from the streaming with flink book,
It says that the timers registered by the trigger are maintained by window operator
At the end,it says that registered trigger timers are not cleared because this state is opaque to the window operator.
The two sentences are contradictory, I would which one is correct? Thanks.
A trigger can register timers to be called back at certain points in
time—for example, to evaluate a window or purge its contents. These timers are maintained by the window operator
Custom-defined state in a trigger
A trigger can define and use custom, per-window and per-key state.
This state is completely controlled by the trigger and not
maintained by the window operator.
The window operator deletes a window when the end time of the
window, defined by the end timestamp of the window object, is
reached. Whether this happens with processing-time or event-time
semantics depends on the value returned by the
WindowAssigner.isEventTime() method.
When a window is deleted, the window operator automatically clears
the window content and discards the window object. Custom-defined
trigger state and registered trigger timers are not cleared because this
state is opaque to the window operator. Hence, a trigger must clear all
of its state in the Trigger.clear() method to prevent leaking
state.
The text was updated successfully, but these errors were encountered:
Hi,
I have quoted the following paragraphs from the streaming with flink book,
It says that the timers registered by the trigger are maintained by window operator
At the end,it says that registered trigger timers are not cleared because this state is opaque to the window operator.
The two sentences are contradictory, I would which one is correct? Thanks.
The text was updated successfully, but these errors were encountered: