[
https://issues.apache.org/jira/browse/FLINK-6118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-6118:
----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor (was:
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.
> Chained operators forward watermark without checking
> ----------------------------------------------------
>
> Key: FLINK-6118
> URL: https://issues.apache.org/jira/browse/FLINK-6118
> Project: Flink
> Issue Type: Bug
> Components: API / DataStream
> Affects Versions: 1.1.4, 1.2.0, 1.3.0
> Reporter: Aljoscha Krettek
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> For operators that read from the network we have checks in place that verify
> that the input watermark only moves forwards. If an operator is directly
> chained to an operator then any {{Output.emitWatermark()}} of the first
> operator directly invoke {{processWatermark()}} on the chained operator,
> meaning that there are no verification steps in-between.
> This only becomes visible when a non-keyed, chained operator (with, for
> example a {{ProcessFunction}}) is checking the current watermark. Only keyed
> operators can have timers and for those the watermark always comes form the
> network, i.e. it behaves correctly.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
