[
https://issues.apache.org/jira/browse/FLINK-18934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17189816#comment-17189816
]
Zhu Zhu commented on FLINK-18934:
---------------------------------
[~knaufk] [~aljoscha] Given that this issue was proposed as a blocker for
releasing 1.11.2, I have a couple of questions to understand the state of it.
Appreciate if you can help with them.
- Should it be a strict blocker of releasing 1.11.2?
- Is there a concise on how we can fix it?
- Does next Monday as the deadline to cut RC1 work for the fix?
> 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
> Affects Versions: 1.11.1
> Reporter: Truong Duc Kien
> Priority: Critical
> Fix For: 1.12.0, 1.11.2
>
>
> 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)
