123123213weqw opened a new issue, #2498:
URL: https://github.com/apache/rocketmq-dashboard/issues/2498

   ## Problem
   
   When a Topic exists on the Broker but has no local `rmq_instance_topic` 
record, the update can write to the Broker successfully yet skip the database 
insert; the returned ID is also null.
   
   Location: 
`server/src/main/java/org/apache/rocketmq/studio/provider/apache/RocketMQAdminClientImpl.java`.
   
   ## Expected behavior
   
   After a successful Broker update, upsert the metadata keyed by cluster + 
instance + topic, reusing the create-path field population rules.
   
   ## Verification
   
   Simulate a Topic present on the Broker but absent locally; after an update 
exactly one correctly-scoped record must be inserted.
   
   Note: do not re-do the existing queue-count issues #2345/#2354.
   


-- 
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]

Reply via email to