Fix topic ownership is not checked when get topic policy (target branch-2.7) #9781
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Currently, the API of topic policies does not check the ownership of topic. In the case of multiple brokers, a
cache not init error
will appear.The parameter validation of the read and write API should not be the same, and the read API should not verify
validatePoliciesReadOnlyAccess()
. IfReadOnly
is set, the read API will also be abnormal.General API should not use
validateAdminAccessForTenant()
.The original PR is #9767