he source so end up as duplicates. I know
>> throwing an exception in the Flink job is not the same as triggering a
>> stateful shutdown, but it might be hitting similar unack issues.
>>
>> John
>>
>> --
>> *From:* Austin Cawley-Edwar
ing an exception in the Flink job is not the same as triggering a
> stateful shutdown, but it might be hitting similar unack issues.
>
> John
>
> --
> *From:* Austin Cawley-Edwards
> *Sent:* Thursday 13 May 2021 16:49
> *To:* Jose Vargas ; John Morr
same as triggering a stateful shutdown,
but it might be hitting similar unack issues.
John
From: Austin Cawley-Edwards
Sent: Thursday 13 May 2021 16:49
To: Jose Vargas ; John Morrow
Cc: user
Subject: Re: RabbitMQ source does not stop unless message arrives in qu
Hey Jose,
Thanks for bringing this up – it indeed sounds like a bug. There is ongoing
work to update the RMQ source to the new interface, which might address
some of these issues (or should, if it is not already), tracked in
FLINK-20628[1]. Would you be able to create a JIRA issue for this, or wou
Hi,
I am using Flink 1.12 to read from and write to a RabbitMQ cluster. Flink's
RabbitMQ source has some surprising behavior when a stop-with-savepoint
request is made.
*Expected Behavior:*
The stop-with-savepoint request stops the job with a FINISHED state.
*Actual Behavior:*
The stop-with-save
