[
https://issues.apache.org/jira/browse/FLINK-20443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-20443:
-----------------------------------
Labels: pull-request-available stale-minor (was: pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I noticed that neither this issue nor its
subtasks had updates for 180 days, so I labeled it "stale-minor". If you are
still affected by this bug or are still interested in this issue, please update
and remove the label.
> ContinuousProcessingTimeTrigger doesn't fire at the end of the window
> ---------------------------------------------------------------------
>
> Key: FLINK-20443
> URL: https://issues.apache.org/jira/browse/FLINK-20443
> Project: Flink
> Issue Type: Improvement
> Components: API / DataStream
> Reporter: Gee
> Priority: Minor
> Labels: pull-request-available, stale-minor
>
>
> {code:java}
> srcStream
> .timeWindowAll(Time.seconds(60))
> .trigger(ContinuousProcessingTimeTrigger.of(Time.seconds(10)))...
> {code}
>
> This can correctly calculate the following interval result : 0-10s 10-20s
> 20-30s 30-40s 40-50s
> But this lost data which was send in 50-60s.
> Because when the first window ends, the time is 59.9999s, it is not equal to
> window-end-time(60s).So it will not enter the if judgment.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
