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.

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

Fix wrong results of hasMessageAvailable and readNext after seeking by timestamp #422

Merged

Conversation

BewareMyPower
Copy link
Contributor

Fixes #420

It's a catch-up for apache/pulsar#22363

@BewareMyPower BewareMyPower added bug Something isn't working release/3.5.1 labels Mar 27, 2024
@BewareMyPower BewareMyPower self-assigned this Mar 27, 2024
@BewareMyPower BewareMyPower merged commit 27d8cc0 into apache:main Mar 28, 2024
15 checks passed
@BewareMyPower BewareMyPower deleted the bewaremypower/fix-seek-by-ts branch March 28, 2024 02:36
BewareMyPower added a commit that referenced this pull request Mar 28, 2024
…y timestamp (#422)

Fixes #420

It's a catch-up for apache/pulsar#22363

(cherry picked from commit 27d8cc0)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working release/3.5.1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug] Regression of seeking by timestamp in 3.5.0
2 participants