Aias00 opened a new issue, #918: URL: https://github.com/apache/rocketmq-dashboard/issues/918
### Description In mock mode, `createTopic()` inserts a new topic without checking whether the same cluster already has a topic with the same name. Location: - `web/src/services/topicService.ts:32` The same service later updates and deletes topics by name, so duplicate topic names in one cluster make subsequent actions ambiguous and can mutate/delete the first matching row instead of the row the user intended. This is different from #739, which tracks the larger cross-cluster identity problem for topic actions. This issue is limited to rejecting duplicate creates within the same cluster in the mock service. ### Impact The Topic page can show duplicate rows for the same topic name in one cluster. Follow-up update/delete/detail actions then operate on a name-only lookup and may affect the wrong row. ### Suggested fix Before inserting a mock topic, reject creates when another topic in the same `clusterId` already has the requested `name`. Add regression coverage that the duplicate create is rejected and the existing topic row remains unchanged. -- 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]
