[
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 stale-minor
(was: auto-deprioritized-critical auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or 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: Minor
> Labels: auto-deprioritized-critical, auto-deprioritized-major,
> stale-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)
