RockteMQ-AI commented on issue #1109: URL: https://github.com/apache/rocketmq-dashboard/issues/1109#issuecomment-5201503716
**Issue Evaluation** Category: | Status: **Evaluated** The issue correctly identifies a design gap: Topic and Consumer Group list APIs transfer all records and rely on client-side filtering, even though the TypeScript model already exposes and the database schema stores per record. **Assessment:** - **Feasibility:** Feasible. The change is a straightforward propagation of an existing parameter through controller → service → → MyBatis predicates. - **Scope:** Backend (API + service + MyBatis) and frontend (instance-scoped list requests). Well-bounded. - **Compatibility:** Backward compatible — unscoped callers retain existing behavior. - **Acceptance criteria** are clear and testable. **Note:** Server-side filtering is the correct architectural direction. Client-side filtering of unbounded lists does not scale and creates inconsistency with the persisted schema. **Related PR:** #1110 --- *Automated evaluation by github-manager* -- 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]
