Aias00 opened a new issue, #1109: URL: https://github.com/apache/rocketmq-dashboard/issues/1109
## Problem Studio instance routes select an `instanceId`, but Topic and Consumer Group pages currently fetch all persisted records and filter them only in the browser. The TypeScript topic query model already exposes `instanceId`, yet `/api/topics` does not accept or propagate it. Consumer Group lists have the same gap. This transfers unrelated metadata, makes the selected-instance context non-authoritative at the API boundary, and leaves list behavior inconsistent with the persisted `rmq_topic.instance_id` and `rmq_group.instance_id` columns. ## Scope - Accept an optional `instanceId` on Topic and Consumer Group list APIs. - Propagate it through controller, service, and `MetadataProvider`. - Add the matching MyBatis predicates. - Make the instance pages request the selected instance rather than filtering a full response locally. - Keep unscoped calls backward compatible. ## Out of scope Resource detail and write identity remain tracked by #739 and #740; this change only scopes list reads. ## Acceptance criteria - `GET /api/topics?instanceId=...` and `GET /api/groups?instanceId=...` return only records for that instance. - The selected instance is present in frontend list requests. - Unscoped callers retain the existing behavior. - Backend and frontend regression tests cover scoped and unscoped requests. -- 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]
