Module sink 

RabbitMQ sink: publisher-confirmed, optionally mandatory publishes to one exchange.

Publishes are pipelined within max.pending messages and max.pending.bytes; flush (and therefore every checkpoint’s pre-commit) waits until the broker has confirmed each one. A confirm means the broker accepted the message for every queue it routed to; durable storage additionally needs persistent delivery mode and durable (for node loss, replicated) queues, which the operator provisions. Any nack, return, or lost outcome ends this sink generation; replay from the last checkpoint may then publish duplicates (at-least-once).

Structs

RabbitMqSink

RabbitMQ AMQP 0-9-1 exchange sink.