orcing the whole job to adopt aligned watermarks.
>
>
>
> What do you think?
>
>
>
> Regards
>
>
>
> Thias
>
>
>
>
>
> *From:* Alexis Sarda-Espinosa
> *Sent:* Tuesday, February 28, 2023 7:57 AM
> *To:* Mason Chen
> *Cc:* Remigiusz Janec
adopt aligned watermarks.
What do you think?
Regards
Thias
From: Alexis Sarda-Espinosa
Sent: Tuesday, February 28, 2023 7:57 AM
To: Mason Chen
Cc: Remigiusz Janeczek ; user
Subject: Re: Fast and slow stream sources for Interval Join
⚠EXTERNAL MESSAGE – CAUTION: Think Before You Click ⚠
Hi
Hi Mason,
Very interesting, is it possible to apply both types of alignment? I.e.,
considering watermark skew across splits from within one source & also from
another source?
Regards,
Alexis.
On Tue, 28 Feb 2023, 05:26 Mason Chen, wrote:
> Hi all,
>
> It's true that the problem can be handled
Hi all,
It's true that the problem can be handled by caching records in state.
However, there is an alternative using `watermark alignment` with Flink
1.15+ [1] which does the desired synchronization that you described while
reducing the size of state from the former approach.
To use this with tw
Hello,
I had this question myself and I've seen it a few times, the answer is
always the same, there's currently no official way to handle it without
state.
Regards,
Alexis.
On Mon, 27 Feb 2023, 14:09 Remigiusz Janeczek, wrote:
> Hi,
>
> How to handle a case where one of the Kafka topics used
Hi,
How to handle a case where one of the Kafka topics used for interval join
is slower than the other? (Or a case where one topic lags behind)
Is there a way to stop consuming from the fast topic and wait for the slow
one to catch up? I want to avoid running out of memory (or keeping a very
larg
