[improve][pcip] PCIP-5 Support Pull Consumer For Pulsar #13
Conversation
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
liangyepianzhou
force-pushed
the
pull_consumer
branch
from
ce40d17 to
809f918
Compare
liangyepianzhou
force-pushed
the
pull_consumer
branch
from
94afb2e to
555ae3d
Compare
liangyepianzhou
force-pushed
the
pull_consumer
branch
from
555ae3d to
72e2f4f
Compare
liangyepianzhou
requested review from
BewareMyPower,
Demogorgon314,
dao-jun,
eolivelli and
nodece
Member
|
Change the title to |
liangyepianzhou
changed the title
liangyepianzhou
force-pushed
the
pull_consumer
branch
2 times, most recently
from
025b80d to
2a988fa
Compare
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
liangyepianzhou
force-pushed
the
pull_consumer
branch
from
025b80d to
2a988fa
Compare
Member
|
@liangyepianzhou Let's shut this down. I've submitted a new one based on the new format and some feature fixes. The link is #24 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Motivation
Our organization is currently planning a migration from RocketMQ to Pulsar. To facilitate this transition, we aim to implement a standardized abstraction layer for MQ clients that encapsulates implementation details of specific messaging systems. This abstraction layer will allow seamless engine replacement while maintaining consistent client interfaces. However, two critical compatibility issues hinder the unification of message fetching patterns between RocketMQ/Kafka and Pulsar:
Interface Disparity:
Pulsar currently lacks native support for offset-based message fetching (fetch/pull paradigm) that allows specifying exact message positions and batch sizes.
Positioning Mechanism Mismatch:
Therefore, I propose to contribute a customized feature implementation to the Pulsar contributor repository that leverages existing Pulsar APIs to achieve functionality similar to RocketMQ's pull consumer. This implementation could serve companies like ours with standardized client requirements, allowing them to reuse this solution.
Modifications
Implement RocketMQ-like pull consumer functionality using existing Pulsar APIs.
Verifying this change
(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)