Aias00 opened a new issue, #4141: URL: https://github.com/apache/rocketmq-dashboard/issues/4141
## Problem In mock mode, Topic reads already respect `instanceId`, but mutations do not consistently use the same resource identity: - duplicate detection in `createTopic` compares only Topic name and cluster; - `updateTopic` selects the first matching Topic name; - `deleteTopic` removes the first matching Topic name. The real persistence model allows the same `(cluster_id, name)` in different instances because its unique key is `(cluster_id, instance_id, name)`. In mock mode, creating the same Topic in a second instance is rejected, while update or delete can affect the matching row from another instance. This makes demo and test behavior diverge from the real API. ## Expected behavior - Mock Topic duplicate detection includes `instanceId` when it is supplied. - The same Topic name and cluster may exist in different instances. - Mock update and delete affect only the Topic belonging to the requested instance. - Existing legacy calls that omit `instanceId` keep their current behavior. ## Acceptance criteria - Add regression coverage for same-name Topics in two instances. - Verify a duplicate in the same instance is still rejected. - Verify update changes only the requested instance. - Verify delete removes only the requested instance. - Do not change the real backend API contract or persistence schema. ## Scope Frontend mock service and focused unit tests only. -- 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]
