If we don't do this then we run the risk of committing offsets for
messages that may not have been handled yet. It exposes consumers to the
possibility of consuming messages more than once, but makes this wrapper
behave closer to how Kafunk does in terms of at-least-once semantics.
Await
handle
before storing new offsetsIf we don't do this then we run the risk of committing offsets for messages that may not have been handled yet. It exposes consumers to the possibility of consuming messages more than once, but makes this wrapper behave closer to how Kafunk does in terms of at-least-once semantics.
Addresses one of the concerns raised in #9.