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

[pulsar-broker] Add get-last-message-id admin for v1 api #8081

Merged
merged 1 commit into from
Sep 30, 2020

Conversation

rdhabalia
Copy link
Contributor

Motivation

#3196 has added getLastMessageId api for v2-admin api but system with legacy topics-v1 also require this api. So, adding getLastMessageId support for V1 api as well.

@codelipenghui
Copy link
Contributor

/pulsarbot run-failure-checks

1 similar comment
@rdhabalia
Copy link
Contributor Author

/pulsarbot run-failure-checks

@codelipenghui codelipenghui merged commit 13ef85a into apache:master Sep 30, 2020
lbenc135 pushed a commit to lbenc135/pulsar that referenced this pull request Oct 3, 2020
### Motivation

apache#3196 has added `getLastMessageId` api for v2-admin api but system with legacy topics-v1 also require this api. So, adding getLastMessageId support for V1 api as well.
wolfstudy pushed a commit that referenced this pull request Oct 30, 2020
### Motivation

#3196 has added `getLastMessageId` api for v2-admin api but system with legacy topics-v1 also require this api. So, adding getLastMessageId support for V1 api as well.

(cherry picked from commit 13ef85a)
huangdx0726 pushed a commit to huangdx0726/pulsar that referenced this pull request Nov 13, 2020
### Motivation

apache#3196 has added `getLastMessageId` api for v2-admin api but system with legacy topics-v1 also require this api. So, adding getLastMessageId support for V1 api as well.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants