This sounds very much like our issue, thank you! We will follow along with
the bug.
Much appreciated,
- Reem
On Thu, Mar 30, 2023 at 9:20 AM Martijn Visser
wrote:
> Hi Reem
>
> My thinking is that this might be related to recently reported
> https://issues.apache.org/jira/browse/FLINK-31632.
>
Hi Reem
My thinking is that this might be related to recently reported
https://issues.apache.org/jira/browse/FLINK-31632.
Best regards,
Martijn
On Wed, Mar 29, 2023 at 7:07 PM Reem Razak via user
wrote:
> Hey Martijn,
>
> The version is 1.16.0
>
> On Wed, Mar 29, 2023 at 5:43 PM Martijn Visse
Hey Martijn,
The version is 1.16.0
On Wed, Mar 29, 2023 at 5:43 PM Martijn Visser
wrote:
> Hi Reem,
>
> What's the Flink version where you're encountering this issue?
>
> Best regards,
>
> Martijn
>
> On Wed, Mar 29, 2023 at 5:18 PM Reem Razak via user
> wrote:
>
>> Hey there!
>>
>> We are see
Hi Reem,
What's the Flink version where you're encountering this issue?
Best regards,
Martijn
On Wed, Mar 29, 2023 at 5:18 PM Reem Razak via user
wrote:
> Hey there!
>
> We are seeing a second Flink pipeline encountering similar issues when
> configuring both `withWatermarkAlignment` and `wit
Hey there!
We are seeing a second Flink pipeline encountering similar issues when
configuring both `withWatermarkAlignment` and `withIdleness`. The
unexpected behaviour gets triggered after a Kafka cluster failover. Any
thoughts on there being an incompatibility between the two?
Thanks!
On Wed,
