btlqql opened a new issue, #6647: URL: https://github.com/apache/rocketmq-dashboard/issues/6647
### Version and verification `rocketmq-studio` at `e2f815fba774a1e399bf9bb3709246edca1a436d`, checked by tracing the frontend table definitions and their paged fetches. This report does not claim a live deployment or browser reproduction. ### Problem Four more server-paginated tables expose antd in-memory sorters. Their data sources hold one server page, so a header click reorders only that page while the sort indicator suggests the entire result set is ordered: | Page | Current sorter declarations | | --- | ---: | | `web/src/pages/ops/audit.tsx` | 6 | | `web/src/pages/ops/alerts.tsx` | 6 | | `web/src/pages/instance/consumer.tsx` | 8 | | `web/src/pages/instance/topic.tsx` | 5 | For example, with multiple consumer pages, sorting the `totalLag` column changes the visible page order but does not find the highest-lag group across all pages. The paged fetches do not receive the selected sort field and direction. ### Expected behavior Either send a validated sort field and direction to the backend and apply that order before pagination, or remove sort controls that only reorder the current page. Regression tests should cover each affected server-paginated table. ### Related work - #5335 handles the message and DLQ tables only. - #5996 tracks the ACL tables separately. - #4610 previously reported the audit and alert tables; the stale bot closed it without a merged 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]
