[improve][pip] PIP-435: Add startTimestamp and endTimestamp for consuming messages in client cli #24524
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
Merged
15 tasks
There was a problem hiding this comment.
Pull Request Overview
Adds a design proposal for new startTimestamp and endTimestamp options to the Pulsar client CLI to allow users to consume messages within a specific time range.
- Introduces CLI flags and describes seek-and-stop logic in the design doc
- Outlines placeholders for compatibility, scope, and alternatives
- References mailing list threads for discussion
Comments suppressed due to low confidence (6)
pip/pip-435.md:13
- Populate the 'In Scope' section with specific items that will be implemented in this PIP, or remove the heading if no additional scope details are needed.
## In Scope
pip/pip-435.md:16
- Populate the 'Out of Scope' section to clarify what is intentionally excluded from this enhancement or remove the heading.
## Out of Scope
pip/pip-435.md:32
- Describe any backward or forward compatibility implications of adding these flags or remove the section if none exist.
# Backward & Forward Compatibility
pip/pip-435.md:35
- List possible alternatives considered for this design or remove the section if not needed.
# Alternatives
pip/pip-435.md:41
- Provide the URL for the voting thread or remove this placeholder if the link is not yet available.
* Mailing List voting thread:
pip/pip-435.md:30
- Add tests to validate that the consumer correctly seeks to
startTimestampand stops atendTimestampduring message consumption.
Then use `consumer.seek(startTimestamp)` to consume the messages from the specified start timestamp, and check the `publishTime` of the received msg, if larger than the `endTimestamp`, stop the consume process.
poorbarcode
approved these changes
Jul 18, 2025
… read Entries (apache#24519)" This reverts commit 5bb6d69.
codelipenghui
approved these changes
Jul 18, 2025
liangyepianzhou
approved these changes
Jul 18, 2025
crossoverJie
approved these changes
Jul 18, 2025
dao-jun
approved these changes
Jul 19, 2025
KannarFr
pushed a commit
to CleverCloud/pulsar
that referenced
this pull request
Sep 22, 2025
…ming messages in client cli (apache#24524) Co-authored-by: Yunze Xu <xyzinfernity@163.com>
walkinggo
pushed a commit
to walkinggo/pulsar
that referenced
this pull request
Oct 8, 2025
…ming messages in client cli (apache#24524) Co-authored-by: Yunze Xu <xyzinfernity@163.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 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
Currently, if users consume messages from a topic using the Pulsar client CLI, they can't have an option to consume messages from a specific time. This PIP proposes to add
startTimestampandendTimestampoptions to the Pulsar client CLI to allow users to consume messages within a specific time range.Modifications
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:)
Does this pull request potentially affect one of the following parts:
If the box was checked, please highlight the changes
Documentation
docdoc-requireddoc-not-neededdoc-completeMatching PR in forked repository
PR in forked repository: