Yes, The current implementation doesn't leverage transactions on publish
like it does for the source on acking and nacking the deliveries, you can
raise a ticket to support exactly once RMQSinks within the community or
implement the logic yourself.
my checkpoints size is increasing. can this
Hi Banu,
This behavior of source is expected, the guarantee of the RMQSource is
exactly once which is achieved by acknowledging envelopes on checkpoints
hence the source would never re-read a message after checkpoint even if it
was still inside the pipeline and not yet passed to sink, eager
acknowl
Hi All,
Gentle reminder about bow query.
Thanks
Banu
On Tue, 9 Jul, 2024, 1:42 pm banu priya, wrote:
> Hi All,
>
> I have a Flink job with a RMQ source, tumbling windows (fires for each
> 2s), an aggregator, then a RMQ sink. Incremental RocksDB checkpointing is
> enabled with an interval of 5
Hi All,
I have a Flink job with a RMQ source, tumbling windows (fires for each 2s),
an aggregator, then a RMQ sink. Incremental RocksDB checkpointing is
enabled with an interval of 5 minutes.
I was trying to understand Flink failure recovery. My checkpoint X is
started, I have sent one event to m
