RockteMQ-AI commented on issue #2498: URL: https://github.com/apache/rocketmq-dashboard/issues/2498#issuecomment-5368439644
**Issue Evaluation** Category: `bug` | Status: **Confirmed** The reported issue has been verified against the current codebase. **Root Cause:** In `RocketMQAdminClientImpl.updateTopic()` (line ~260), the DB update is guarded by `if (existing != null)`. When a topic exists on the broker but has no local `rmq_instance_topic` record (`existing == null`), the broker config update succeeds but no DB insert follows. The local metadata remains missing. **Impact:** Topic metadata is lost when updating broker-discovered topics that have no prior DB record. Subsequent queries show inconsistent state. **Severity:** medium **Suggested Fix:** When `existing == null`, create a new `RmqTopic` record (upsert) keyed by cluster + instance + topic, reusing the create-path field population rules. An automated fix proposal will be generated. Reply `/approve` to proceed with PR generation. --- *Automated evaluation by github-manager* -- 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]
