Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Reading position manipulation #135

Closed
DongbinNie opened this issue Dec 2, 2016 · 4 comments
Closed

Reading position manipulation #135

DongbinNie opened this issue Dec 2, 2016 · 4 comments
Labels
type/feature The PR added a new feature or issue requested a new feature

Comments

@DongbinNie
Copy link

Reading position manipulation, that the reading position can be adjusted backward or forward.

[Andrew]
You can skip and rewind via the admin client.

[merlimat]
In general we've tried to stay away from that because it clashes a bit with pub/sub model. What would be the use case for these manipulations? And what the interactions would look like?

[DongbinNie]
There's various circumstance needing to replay the messages, such as re-building the search indexes on restarting.
I didn't noticed it can be skipped and rewinded via the admin client, com.yahoo.pulsar.client.admin.PersistentTopics.resetCursor(String, String, long), maybe We can also reset the cursor based on message id.
@merlimat
Copy link
Contributor

merlimat commented Dec 3, 2016

maybe We can also reset the cursor based on message id.

actually the replay feature only works with a "timestamp". The main reason is that rolling back to a specific messageId would be impossible to do on a partitioned topic.

@merlimat merlimat added the type/feature The PR added a new feature or issue requested a new feature label Dec 3, 2016
@merlimat merlimat changed the title [Feature Proposal] Reading position manipulation Reading position manipulation Dec 3, 2016
@DongbinNie
Copy link
Author

The main reason is that rolling back to a specific messageId would be impossible to do on a partitioned topic.

The application may provide messageIds for each partition, but timestamp already meets most of the replay cases in application, :-)

sijie pushed a commit to sijie/pulsar that referenced this issue Mar 4, 2018
@srkukarni @sijie
First cut of Python Instance that just parses the arguments and start… (
fea9805 
apache#135)

* First cut of Python Instance that just parses the arguments and starts a server to process incoming requests

* Add license header
@ivankelly
Copy link
Contributor

@merlimat @DongbinNie
Is this solved by ReaderBuilder#startMessageId?
http://pulsar.apache.org/api/client/org/apache/pulsar/client/api/ReaderBuilder.html#startMessageId-org.apache.pulsar.client.api.MessageId-

@ivankelly
Copy link
Contributor

Closing due to lack of activity. Feel free to reopen.

hangc0276 pushed a commit to hangc0276/pulsar that referenced this issue May 26, 2021
@aloyszhang
apache#135 fix IllegalArgumentException for KafkaConsumer#offsetsForT…
d70dde9 
…imes (apache#137)

 Fix IllegalArgumentException for  KafkaConsumer#offsetsForTimes under kafka versions of 2.1.0 , 2.2.0 and 2.3.0
@xiaotongwang1 xiaotongwang1 mentioned this issue Aug 4, 2021
Closed
@ZHr-UChiHa ZHr-UChiHa mentioned this issue Jun 3, 2023
Open
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type/feature The PR added a new feature or issue requested a new feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ivankelly @merlimat @DongbinNie