Frun1na opened a new issue, #4935: URL: https://github.com/apache/rocketmq-dashboard/issues/4935
### Before Creating the Bug Report - [x] I have searched the [open issues](https://github.com/apache/rocketmq-dashboard/issues) of this repository and believe that this is not a duplicate. - [x] This is a defect in RocketMQ Studio, not a usage question and not a defect in another Apache RocketMQ repository. - [x] I can reproduce this on the current `master` branch, or I have stated the exact version I am running below. ### Studio Version branch: `rocketmq-studio` git commit id: `1ef5d860` (upstream tip at the time of the report) deployed as: built from source ### Runtime Environment Verified by code tracing and unit tests on `rocketmq-studio` @ `1ef5d860` (vitest for `web/`, JUnit for `server/`), not against a specific browser or deployment. ### Connected RocketMQ Cluster Not cluster-specific: the defect lives in the code path and reproduces on any deployment where the trigger condition below holds. ### Describe the Bug Tables whose data is fetched with server-side pagination still declared antd in-memory `sorter` functions on some columns (message storeTime/topic; DLQ group name/messageCount). Sorting applies to the current page only and silently misrepresents the ordering of the full result set. ### Steps to Reproduce 1. Query messages by topic with enough results for multiple pages. 2. Click the 存储时间 (or Topic) column header to sort. 3. Page 2 continues in the server's original order, so the combined view is not sorted. ### What Did You Expect to See? Sorting either covers the full result set (server-side sort parameter) or is not offered when data is server-paginated. ### What Did You See Instead? A page-local sort is presented as a table-wide sort. -- 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]
