aloyszhang edited a comment on pull request #7848: URL: https://github.com/apache/pulsar/pull/7848#issuecomment-678329438
@codelipenghui Thanks for your reply. I think use `message id` is a alternative way. But I don't think clock time is an issue, since both the `publish time` and `seek time` are specified from the client side. Using `publish time` and `seek time` to decides whether have available messages make sence for me. Think about this case, if we seek at a timestamp after `publish time` of the last message, there **should be no messages available**. But if we use MessageId to decides whether have available messages , 1. the `seek(Timestamp)` will return with the `last messageId` 2. the `getLastMessageId` also return the `last messageId` 3. if `resetIncludeHead` is true `hasMessageAvailable` will return true, and this is not right. So in this case, we should do more border control to keep it works well. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
