-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
[Branch-2.7][Broker] Fix using partitioned topic name to get topic policies #11897
[Branch-2.7][Broker] Fix using partitioned topic name to get topic policies #11897
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. left one comment.
@@ -593,8 +593,6 @@ public void testTlsEnabledWithoutNonTlsServicePorts() throws Exception { | |||
|
|||
} catch (Exception e) { | |||
fail("should not fail"); | |||
} finally { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why delete this code?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If close the pulsarClient
, it will cause other test methods can't use the pulsarClient
and there is a clean operation after the test.
Motivation
There is a bug that using the partitioned topic name to get topic policies. The PR #11294 fix this issue, but it's hard to cherry-pick the PR to
branch-2.7
, so create this PR to fix the issue inbranch-2.7
.This PR contains PR-11294 and PR-11863.
Modifications
Verifying this change
The test method
TopicPoliciesTest#testBacklogQuotaWithPartitionedTopic
is used to verify getting topic policies by the partitioned topic name.Does this pull request potentially affect one of the following parts:
If
yes
was chosen, please highlight the changesDocumentation
Check the box below and label this PR (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)