BewareMyPower opened a new pull request, #21945: URL: https://github.com/apache/pulsar/pull/21945
### Motivation The multi-topics consumer supports seeking all internal consumers when accepting a timestamp as the argument. However, the multi-topics consumer could still read from earliest after seeking to a specific position. It's because before an internal consumer completes a seek operation, it could still receive duplicated messages. ### Modifications For a multi-topics consumer, before the seek operation is done, do not call `messageReceived` method. Once the seek operation is done, collect all messages from internal consumers and call `messageReceived` method for each one. Add `testSeekByTimestamp` to verify `receive`, `receiveAsync` and message listener all work for seeking by timestamp on a multi-topics consumer. ### Documentation <!-- DO NOT REMOVE THIS SECTION. CHECK THE PROPER BOX ONLY. --> - [ ] `doc` <!-- Your PR contains doc changes. --> - [ ] `doc-required` <!-- Your PR changes impact docs and you will update later --> - [x] `doc-not-needed` <!-- Your PR changes do not impact docs --> - [ ] `doc-complete` <!-- Docs have been already added --> ### Matching PR in forked repository PR in forked repository: -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
