lement2 a single time? How does the
> framework decide when to switch the stream processing when the streams are
> connected?
>
>
>
> Regards,
>
> Alexis.
>
>
>
> *From:* David Morávek
> *Sent:* Donnerstag, 2. Dezember 2021 17:18
> *To:* Alexis Sarda-Espinos
a
mailto:alexis.sarda-espin...@microfocus.com>>
Cc: user@flink.apache.org<mailto:user@flink.apache.org>
Subject: Re: Buffering when connecting streams
Even with the TwoInputStreamOperator you can not "halt" the processing. You
need to buffer these elements for example in the ListState f
pin...@microfocus.com> wrote:
>>
>> Yes, that sounds right, but with my current KeyedCoProcessFunction I
>> can’t tell Flink to "halt" processElement1 and switch to the other stream
>> depending on watermarks. I could look into TwoInputStreamOperator
gt;
>
> *From:* David Morávek
> *Sent:* Donnerstag, 2. Dezember 2021 17:18
> *To:* Alexis Sarda-Espinosa
> *Cc:* user@flink.apache.org
> *Subject:* Re: Buffering when connecting streams
>
>
>
> Even with the TwoInputStreamOperator you can not "halt" the pro
. Dezember 2021 17:18
To: Alexis Sarda-Espinosa
Cc: user@flink.apache.org
Subject: Re: Buffering when connecting streams
Even with the TwoInputStreamOperator you can not "halt" the processing. You
need to buffer these elements for example in the ListState for later
processing. At the t
k
> *Sent:* Donnerstag, 2. Dezember 2021 16:59
> *To:* Alexis Sarda-Espinosa
> *Cc:* user@flink.apache.org
> *Subject:* Re: Buffering when connecting streams
>
>
>
> I think this would require using lower level API and implementing a custom
> `TwoInputStreamOperator`. T
ávek
Sent: Donnerstag, 2. Dezember 2021 16:59
To: Alexis Sarda-Espinosa
Cc: user@flink.apache.org
Subject: Re: Buffering when connecting streams
I think this would require using lower level API and implementing a custom
`TwoInputStreamOperator`. Then you can hook to `processWatemark{1,2}` metho
> Alexis.
>
>
>
> *From:* David Morávek
> *Sent:* Donnerstag, 2. Dezember 2021 15:45
> *To:* Alexis Sarda-Espinosa
> *Cc:* user@flink.apache.org
> *Subject:* Re: Buffering when connecting streams
>
>
>
> You can not rely on order of the two streams that
reaches
processElement1, even when considering watermarks.
Regards,
Alexis.
From: David Morávek
Sent: Donnerstag, 2. Dezember 2021 15:45
To: Alexis Sarda-Espinosa
Cc: user@flink.apache.org
Subject: Re: Buffering when connecting streams
You can not rely on order of the two streams that easily. In
from open
> to close) triggered on second 17, and my windows are evaluated every
> minute, so it wasn’t a race condition.
>
>
>
> Regards,
>
> Alexis.
>
>
>
> *From:* David Morávek
> *Sent:* Donnerstag, 2. Dezember 2021 14:52
> *To:* Alexis Sarda-Espinosa
n
second 17, and my windows are evaluated every minute, so it wasn’t a race
condition.
Regards,
Alexis.
From: David Morávek
Sent: Donnerstag, 2. Dezember 2021 14:52
To: Alexis Sarda-Espinosa
Cc: user@flink.apache.org
Subject: Re: Buffering when connecting streams
Hi Alexis,
I'm not s
Hi Alexis,
I'm not sure what "watermark" step refers to in you graph, but in general
I'd say your intuition is correct.
For the "buffering" part, each sub-task needs to send data via data
exchange (last operator in chain) has an output buffer and the operator
that consumes this data (maybe on dif
12 matches
Mail list logo
