Details
-
Bug
-
Status: Resolved
-
P2
-
Resolution: Duplicate
-
None
-
None
Description
Using the RabbitMqIO as an unbounded source I encounter exceptions when messages are acknowledged.
Reading the code of the IO I understood that ACK are sent when finalizeCheckpoint is called.
If I understand the exception well, it's raised when messages are not acked in same order as they arrive to the system.
Is there something I can do in my pipeline to avoid this exception ? Maybe something needs to be done on RabbitMQ side.
Thanks for your help