X-LightYear opened a new issue, #7191: URL: https://github.com/apache/rocketmq-dashboard/issues/7191
### Describe the Bug The consumer-group export API exposes the same instance/cluster query contract as the paginated group list, but `clusterId` is dropped by the REST controller and MetadataService. Exporting from an instance containing multiple clusters can therefore include groups from another cluster. ### Production path `web/src/api/metadata.ts` → `GET /api/groups/export` → `ConsumerGroupController.exportConsumerGroups` → `MetadataService.exportConsumerGroups` → `listConsumerGroups`. ### Reproduction 1. Configure `instance-a` with `group-a` in `cluster-a` and `group-b` in `cluster-b`. 2. Request `GET /api/groups/export?instanceId=instance-a&clusterId=cluster-a`. 3. Observe both groups in the CSV. ### Expected Only `group-a` is exported. ### Actual The export includes `group-a` and `group-b` because `clusterId` is not forwarded to the instance-scoped metadata query. ### Evidence A deterministic service/controller regression covers the two-cluster scenario and passes after forwarding the filter; the affected production path had no parameter carrying `clusterId` before this fix. -- 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]
