yyqdbngt opened a new issue, #2345: URL: https://github.com/apache/rocketmq-dashboard/issues/2345
### Description Updating an existing Apache RocketMQ topic with explicit positive read/write queue counts does not resize the topic. The update path currently prefers the queue counts stored in the metadata row before it considers the values in the request. For example, if an existing topic has 8 read/write queues and an update requests 16 write queues and 12 read queues, the dashboard sends 8/8 to each broker and returns 8/8. ### Expected behavior Positive queue counts supplied by the update request should take precedence. When a partial update omits queue counts, the existing positive values should still be preserved; only a missing value with no usable persisted value should fall back to 8. ### Proposed fix Change the queue-count precedence to request value, then persisted value, then default, and add a regression test that captures the `TopicConfig` sent to the broker and verifies the persisted and returned values. -- 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]
