hanmz opened a new pull request, #22397: URL: https://github.com/apache/pulsar/pull/22397
### Motivation When the configuration `maxNumPartitionsPerPartitionedTopic` <= 0, we should consider the check to be disabled. However, the behavior has been modified in this PR: https://github.com/apache/pulsar/pull/19166 This will cause an error. We will see the following log if `maxNumPartitionsPerPartitionedTopic<0` when update topic partition. `WARN org.apache.pulsar.client.admin.internal.BaseResource - [http://localhost:8080/admin/v2/persistent/test-tenant/test-ns/test-topic/partitions?updateLocalTopicOnly=false&force=false] Failed to perform http post request: javax.ws.rs.ClientErrorException: HTTP 422 {"reason":"Desired partitions 2 can't be greater than the maximum partitions per topic -1."} Desired partitions 2 can't be greater than the maximum partitions per topic -1.` ### Modifications `brokerMaximumPartitionsPerTopic != 0` => `brokerMaximumPartitionsPerTopic > 0` ### Documentation <!-- DO NOT REMOVE THIS SECTION. CHECK THE PROPER BOX ONLY. --> - [ ] `doc` <!-- Your PR contains doc changes. --> - [ ] `doc-required` <!-- Your PR changes impact docs and you will update later --> - [x] `doc-not-needed` <!-- Your PR changes do not impact docs --> - [ ] `doc-complete` <!-- Docs have been already added --> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
