[
https://issues.apache.org/jira/browse/FLINK-18934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dawid Wysakowicz updated FLINK-18934:
-------------------------------------
Release Note: We added `processWatermarkStatusX` method to classes such as
`AbstractStreamOperator`, `Input` etc. It allows to take the `WatermarkStatus`
into account when combining watermarks in two/multi input operators. (was: We
added `processWatermarkStatusX` method to classes such as
`AbstractStreamOperator`, `Input` etc. It allows to take the
{{WatermarkStatus}} into account when combining watermarks in two/multi input
operators.)
> Idle stream does not advance watermark in connected stream
> ----------------------------------------------------------
>
> Key: FLINK-18934
> URL: https://issues.apache.org/jira/browse/FLINK-18934
> Project: Flink
> Issue Type: Bug
> Components: API / DataStream, Runtime / Task
> Affects Versions: 1.11.0, 1.12.0, 1.13.0
> Reporter: Truong Duc Kien
> Assignee: Dawid Wysakowicz
> Priority: Critical
> Labels: pull-request-available, stale-assigned
> Fix For: 1.14.0
>
>
> Per Flink documents, when a stream is idle, it will allow watermarks of
> downstream operator to advance. However, when I connect an active data stream
> with an idle data stream, the output watermark of the CoProcessOperator does
> not increase.
> Here's a small test that reproduces the problem.
> https://github.com/kien-truong/flink-idleness-testing
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
