We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Should we support get offset based on timestamp?
The text was updated successfully, but these errors were encountered:
[Issue 10896] add get message id by timestamp (#11139)
a7e40ea
Fixes #10896 ### Motivation Add getMessageIdByTimestamp in pulsar admin apis ### Modifications The core searching implementation reuses `org.apache.bookkeeper.mledger.ManagedLedger#asyncFindPosition`. Add client tool for cmd `pulsar-admin topics get-message-id`
[Issue 10896] add get message id by timestamp (apache#11139)
8bbb0a2
Fixes apache#10896 Add getMessageIdByTimestamp in pulsar admin apis The core searching implementation reuses `org.apache.bookkeeper.mledger.ManagedLedger#asyncFindPosition`. Add client tool for cmd `pulsar-admin topics get-message-id`
8c284e0
Fixes apache#10896 ### Motivation Add getMessageIdByTimestamp in pulsar admin apis ### Modifications The core searching implementation reuses `org.apache.bookkeeper.mledger.ManagedLedger#asyncFindPosition`. Add client tool for cmd `pulsar-admin topics get-message-id`
Successfully merging a pull request may close this issue.
Should we support get offset based on timestamp?
The text was updated successfully, but these errors were encountered: