[
https://issues.apache.org/jira/browse/FLINK-5363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16540178#comment-16540178
]
ASF GitHub Bot commented on FLINK-5363:
---------------------------------------
Github user cjolif commented on the issue:
https://github.com/apache/flink/pull/3034
@aljoscha
We regularly empty the window because we can get lengthy windows with a lot
of elements, so it is good get rid of elements we already managed. But then if
we have no more elements and the window event time is triggered it does fire
the window function.
When we will get some spare cycle we are going to give a try to it as you
seem to have fix that according to the JIRA issue?
> Fire timers when window state is currently empty
> ------------------------------------------------
>
> Key: FLINK-5363
> URL: https://issues.apache.org/jira/browse/FLINK-5363
> Project: Flink
> Issue Type: Bug
> Components: DataStream API
> Reporter: Aljoscha Krettek
> Assignee: aitozi
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.6.0
>
>
> Currently, when a {{Trigger}} sets a timer and that timer fires in the future
> at a point when there is currently no data in the window state, then that
> timer is being ignored.
> This is a problem for some users because they manually set cleanup timers and
> they need to be called because the trigger needs to cleanup some state. (For
> normal time windows this is not a problem, but for special cases built on top
> of {{GlobalWindows}} the current behaviour leads to problems.)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
