You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "yuemeng (JIRA)" <ji...@apache.org> on 2018/04/18 09:27:00 UTC
[jira] [Updated] (FLINK-9201) same merge window will be fired twice
if watermark already pass the new merged window
[ https://issues.apache.org/jira/browse/FLINK-9201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
yuemeng updated FLINK-9201:
---------------------------
Summary: same merge window will be fired twice if watermark already pass the new merged window (was: same merge window will fire twice if watermark already pass the window for merge windows)
> same merge window will be fired twice if watermark already pass the new merged window
> -------------------------------------------------------------------------------------
>
> Key: FLINK-9201
> URL: https://issues.apache.org/jira/browse/FLINK-9201
> Project: Flink
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.3.3
> Reporter: yuemeng
> Assignee: yuemeng
> Priority: Blocker
>
> sum with session window,.
> suppose the session gap is 3 seconds and allowedlateness is 60 seconds
> w1,TimeWindow[1,9] had elements,1,2,3,6,will be fired if watermark reached 9
> if a late element (w2,TimeWindow[7,10]) had come but the watermark already at 11.
> w1,w2 will be merged a new window w3 TimeWindow[1,10] and will be register a new timer by call triggerContext.onMerge(mergedWindows),then w3 will be fired later by call triggerContext.onElement(element) because of the watermark pass the w3.
> but w3 will be fired again because of the timer < current watermark.
> that mean w3 will be fired twice because of watermark pass the new merge window w3.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)