Conversation
efcasado
force-pushed
the
pulsar-5
branch
3 times, most recently
from
June 27, 2026 15:24
ffc2a6c to
fd5a133
Compare
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
1 participant
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.
https://pulsar.apache.org/blog/2026/06/23/announcing-apache-pulsar-5-0-m1/
Stream abstraction feels like a step backwards? Whilst it preserves ordering across a changing number of segments (~partitions), we cannot spin up an arbitrary number of parallel consumers using a Key-Shared subscription. That is, orderly parallel consumption is now much more limited than before. The number of parallel consumers is now dictated by the number of segments (~partitions) in the topic.
The scalable producer is somewhat disappointing. Given that the broker knows about the DAG topology and is responsible for coordinating segments, etc. I would have expected for the producer flow to be as simple as sending a keyed message to the broker and let the broker handle it internally. It turns out routing has to be implemented in the client.