You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 30, 2024. It is now read-only.
if we have max_uncommited_events parameter greater then batch_limit then potentially we could receive several batches from the same partition before we commit the offset:
Functions like .successPredicateFuture are kind of like the wild west, you are responsible for how you commit cursors, not sure what we can do to help here?
Let's say we have some asynchronous event batch handler:
Async Handler
if we have max_uncommited_events parameter greater then batch_limit then potentially we could receive several batches from the same partition before we commit the offset:
Subscription
The output
as a result, we have next output:
The problem
If the batch with offset (2939 -2941) fails we do not retry the batch, because of the offset indirectly already committed with 000000000000002942.
The text was updated successfully, but these errors were encountered: