RockteMQ-AI commented on issue #4610: URL: https://github.com/apache/rocketmq-dashboard/issues/4610#issuecomment-5751647234
**Issue Evaluation** Category: `bug` | Status: **Confirmed** The bug is confirmed. Both `audit.tsx` and `alerts.tsx` use server-side pagination (controlled `current`/`total` from the server, data source holds only the current page), but define client-side `sorter` functions on every sortable column. Clicking a column header re-orders only the ~20 visible rows while the sort arrows suggest a full-dataset sort. Additionally, `audit.tsx` sets `defaultSortOrder: 'descend'` on the time column, presenting a sort arrow on first paint that merely restates the server's fixed `ORDER BY gmt_create DESC` for one page — and switching pages loses the sort arrow state entirely. **Root Cause:** Client-side sorters on server-paginated tables create a false impression of global ordering. No `onChange` wiring passes sort parameters to the API. **Impact:** Operators making decisions based on sorted views operate on a page-local reorder of ~20 rows while the rest of the dataset is invisible and unordered. **Severity:** Medium — misleading UI for data-driven operations; no data mutation risk. The minimal fix — removing client sorters from server-paginated columns — is the safest approach. --- *Automated evaluation by RocketMQ AI Assistant* -- 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]
