[ 
https://issues.apache.org/jira/browse/FLINK-26565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504825#comment-17504825
 ] 

Jark Wu commented on FLINK-26565:
---------------------------------

What's the problem with current implementation? Could you give an example and 
unexpected result? 

> Use lateTrigger when the window maxtimestap of data is less than 
> currentwatermark and  it is not discarded because the allow latency parameter 
> -----------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-26565
>                 URL: https://issues.apache.org/jira/browse/FLINK-26565
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table SQL / API, Table SQL / Planner, Table SQL / Runtime
>            Reporter: hehuiyuan
>            Priority: Minor
>              Labels: pull-request-available
>         Attachments: image-2022-03-10-11-27-52-891.png
>
>
> Use lateTrigger when the window maxtimestap of data is less than 
> currentwatermark .
> The data  is not discarded because the allow latency parameter.
> The lateTrigger is set and the window just appeared with this data.
> !image-2022-03-10-11-27-52-891.png|width=543,height=318!



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to