-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Get message by messageId #2912
Labels
Comments
rest api could have bad performance to do this ? |
@foreversunyao I'm not sure ! Maybe better read from bookie straightforward. |
I think reading a message by a message-id is the same as peeking messages. |
1 task
codelipenghui
pushed a commit
that referenced
this issue
Apr 22, 2020
#6331) Fixes #2912 ### Motivation Adding a new command `get-message-by-id` to the pulsar-admin which allows user to look at a single message by providing ledger id and entry id. ### Modifications - pulsar-admin includes the new command `get-message-by-id` - pulsar-broker v1/v2 apis to handle the get-message-by-id request from pulsar-admin - managedCursor to read from ledgers with given ledger id and entry id
huangdx0726
pushed a commit
to huangdx0726/pulsar
that referenced
this issue
Aug 24, 2020
apache#6331) Fixes apache#2912 ### Motivation Adding a new command `get-message-by-id` to the pulsar-admin which allows user to look at a single message by providing ledger id and entry id. ### Modifications - pulsar-admin includes the new command `get-message-by-id` - pulsar-broker v1/v2 apis to handle the get-message-by-id request from pulsar-admin - managedCursor to read from ledgers with given ledger id and entry id
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Is it possible to support a rest api to get message by messageId? For now we can peek the head message but can't query message by messageId.
The text was updated successfully, but these errors were encountered: