SeekBy Timestamp is not working as expected if messages are sent in between the Execution #23949
deepakks-tibco
started this conversation in
General
Replies: 2 comments
-
Which Pulsar version? In Pulsar 4.0.2 there's a known issue with seek, also mentioned in the updated release notes with workaround instructions. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Using Current version 4.0.2 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
If we provide the future timestamp and execute the Consumer activity.
It will start the consumer and wait for the messages to consume after that timestamp. But if we sent the messages in between the consumer still consume the messages before that timestamp.
Created a standalone consumer app. Start producer and standalone consumer with future timestamp example timestamp set as currentTimeMillis()+ 5 min. The consumer starts consuming all messages before timestamp.
Here is the standalone consumer code.
Beta Was this translation helpful? Give feedback.
All reactions