[
https://issues.apache.org/jira/browse/FLINK-21120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17329007#comment-17329007
]
Flink Jira Bot commented on FLINK-21120:
----------------------------------------
This critical issue is unassigned and itself and all of its Sub-Tasks have not
been updated for 7 days. So, it has been labeled "stale-critical". If this
ticket is indeed critical, please either assign yourself or give an update.
Afterwards, please remove the label. In 7 days the issue will be deprioritized.
> Add support for ignore abnormal watermark
> -----------------------------------------
>
> Key: FLINK-21120
> URL: https://issues.apache.org/jira/browse/FLINK-21120
> Project: Flink
> Issue Type: Improvement
> Components: API / DataStream
> Affects Versions: 1.11.1, 1.12.0
> Reporter: zlzhang0122
> Priority: Critical
> Labels: stale-critical
>
> When using eventTime and extract watermark from element timestamp to generate
> BoundedOutOfOrderness waternark, if one of the element timestamp is
> abnormal(assume the timestamp is very big, for example Integer.MAX_VALUE),
> then the watermark became very big too, and then the normal element timestamp
> can not trigger the window bellow any more. I think maybe there can provide a
> option to just ignore the abnormal element timestamp or generate a normal
> watermark base on the current processTime.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
