Skip to content

Conversation

@gaozhangmin
Copy link
Contributor

Master Issue: #13854

Motivation

Avoid call sync method in async rest API for PersistentTopicsBase#internalGetLastMessageId.

Documentation

Check the box below or label this PR directly (if you have committer privilege).

Need to update docs?

  • doc-required

    (If you need help on updating docs, create a doc issue)

  • no-need-doc

    (Please explain why)

  • doc

    (If this PR contains doc changes)

@gaozhangmin gaozhangmin changed the title change async [Broker] Fix call sync method in async rest api for internalGetLastMessageId Jan 21, 2022
@github-actions
Copy link

@gaozhangmin:Thanks for your contribution. For this PR, do we need to update docs?
(The PR template contains info about doc, which helps others know more about the changes. Can you provide doc-related info in this and future PR descriptions? Thanks)

@gaozhangmin
Copy link
Contributor Author

/pulsarbot run-failure-checks

if (!(topic instanceof PersistentTopic)) {
log.error("[{}] Not supported operation of non-persistent topic {}", clientAppId(), topicName);
asyncResponse.resume(new RestException(Status.METHOD_NOT_ALLOWED,
"GetLastMessageId on a non-persistent topic is not allowed"));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

need a return here.

@Anonymitaet
Copy link
Member

@gaozhangmin When submitting a PR, can you provide doc-related info (tick the box) in the PR description? So that Bot can recognize and label your PR correspondingly. Or else Bot labels your PR with doc-info-missing. Thanks.

You can check the instructions for doc labels here

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.

4 participants