[
https://issues.apache.org/jira/browse/FLINK-21120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-21120:
-----------------------------------
Labels: auto-deprioritized-critical auto-deprioritized-major
auto-deprioritized-minor (was: auto-deprioritized-critical
auto-deprioritized-major stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> 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: Not a Priority
> Labels: auto-deprioritized-critical, auto-deprioritized-major,
> auto-deprioritized-minor
>
> 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.20.1#820001)
