[
https://issues.apache.org/jira/browse/FLINK-28719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17578858#comment-17578858
]
Mykyta Mykhailenko commented on FLINK-28719:
--------------------------------------------
Actually, I think I hurried a little. Could you answer a few more questions,
[~chesnay]?
_Let's say we consume the input of op1 and op2 completely, and from all other
inputs consume all watermarks until we hit a record in each._
Could you elaborate on this point? __
* As far as I understand, op1 and op2 should have watermark 1 and 2
respectively, because those subtasks don't have any events in them (besides 1
and 2, of course, which create those watermarks). Then, why do they get the
maximum watermark of 7 after first step?
* Also, why after op1 and op2, op4 and op5 get consumed? Is there any strategy
that dictates in which order to process subtasks?
* Also, why op3 to op7 have such watermarks: W2, W5, W6, W6, W6, after first
step? I thought those subtasks should have watermark of Long.MinValue, because
there were no elements before?
> Mapping a data source before window aggregation causes Flink to stop handle
> late events correctly.
> --------------------------------------------------------------------------------------------------
>
> Key: FLINK-28719
> URL: https://issues.apache.org/jira/browse/FLINK-28719
> Project: Flink
> Issue Type: Bug
> Components: API / DataStream
> Affects Versions: 1.15.1
> Reporter: Mykyta Mykhailenko
> Priority: Major
>
> I have created a
> [repository|https://github.com/mykytamykhailenko/flink-map-with-issue] where
> I describe this issue in detail.
> I have provided a few tests and source code so that you can reproduce the
> issue on your own machine.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
