You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Aljoscha Krettek (Jira)" <ji...@apache.org> on 2020/12/02 14:11:00 UTC

[jira] [Updated] (FLINK-20443) ContinuousProcessingTimeTrigger doesn't fire at the end of the window

     [ https://issues.apache.org/jira/browse/FLINK-20443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aljoscha Krettek updated FLINK-20443:
-------------------------------------
    Summary: ContinuousProcessingTimeTrigger doesn't fire at the end of the window  (was: ContinuousProcessingTimeTrigger lost data in last interval in per window)

> 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
>
>  
> {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)