Consume should only process one message at a time #164
Conversation
This file contains 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
While consumer all pre-fetched messages concurrently is useful, the expected behavior for consume is to only handle one message at a time. Considering introducing a stream method for the concurrently handling of messages.
WyriHaximus
force-pushed
the
0.6.x-consume-should-on-process-one-message-at-a-time
branch
from
889c016 to
20d7d7e
Compare
WyriHaximus
deleted the
0.6.x-consume-should-on-process-one-message-at-a-time
branch
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.
While consumer all pre-fetched messages concurrently is useful, the expected behavior for consume is to only handle one message at a time. Considering introducing a stream method for the concurrently handling of messages.