Add batch listener support for Redis StreamMessageListenerContainer.#3334
Open
wwan13 wants to merge 1 commit intospring-projects:mainfrom
Open
Add batch listener support for Redis StreamMessageListenerContainer.#3334wwan13 wants to merge 1 commit intospring-projects:mainfrom
wwan13 wants to merge 1 commit intospring-projects:mainfrom
Conversation
Signed-off-by: wwan13 <wwan13@naver.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR introduces batch listener support for Redis StreamMessageListenerContainer.
Currently, records are delivered individually through StreamListener even when multiple records are returned from Redis using COUNT. This PR adds a BatchStreamListener abstraction to allow processing multiple records in a single callback.
New APIs (registerBatch, receiveBatch) are introduced to support batch consumption while keeping the existing StreamListener API unchanged for backward compatibility.
Batch processing advances the read offset only after successful listener invocation. In case of failures, records may be redelivered, avoiding message loss.
Closes #3190