X-LightYear opened a new issue, #7189: URL: https://github.com/apache/rocketmq-dashboard/issues/7189
### Describe the Bug The topic export API accepts `clusterId` through the frontend export query contract, but the REST controller and MetadataService drop it when an `instanceId` is supplied. An export from an instance containing multiple clusters therefore includes topics from other clusters. ### Production path `web/src/api/metadata.ts` → `GET /api/topics/export` → `TopicController.exportTopics` → `MetadataService.exportTopics` → `listTopics`. ### Reproduction 1. Configure `instance-a` with `topic-a` in `cluster-a` and `topic-b` in `cluster-b`. 2. Request `GET /api/topics/export?instanceId=instance-a&clusterId=cluster-a`. 3. Observe both topics in the CSV. ### Expected Only topics belonging to `cluster-a` are exported. ### Actual The export includes topics from both clusters because `clusterId` is not forwarded. ### Evidence A deterministic MockMvc regression on latest `upstream/rocketmq-studio` failed with `topic-a + topic-b`; the focused service/controller regression passes after forwarding the filter. -- 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]
