You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/12/01 13:02:00 UTC
[jira] [Updated] (FLINK-20443) ContinuousProcessingTimeTrigger lost
data in last interval in per window
[ https://issues.apache.org/jira/browse/FLINK-20443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated FLINK-20443:
-----------------------------------
Labels: pull-request-available (was: )
> ContinuousProcessingTimeTrigger lost data in last interval in per 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
>
>
> {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)