tju-yxq opened a new issue, #2601: URL: https://github.com/apache/rocketmq-dashboard/issues/2601
## Problem `GET /api/messages/page` delegates to `MessageService.queryMessages(...)`, which records a message-query history entry on every provider query: ```java List<MessageRecordVO> result = queryMessages(instanceId, topic, msgId, tag, key, startTime, endTime); ``` When the user pages through the same message result, every page requests the same provider query and therefore writes another row to `rmq_message_query`. The browser’s local query history already avoids duplicate entries for pagination, but the server-side history database does not. For a query returning several pages, the server history becomes: - page 1 → one history row - page 2 → another identical history row - page 3 → another identical history row This inflates the server query history and summary counts without representing a distinct user query. ## Expected behavior - Preserve history recording for direct message queries. - Record server history for the first page of a paginated message query. - Do not write duplicate history rows for subsequent pages of the same paginated result. - Keep provider behavior and page slicing unchanged. ## Verification scope A focused service test should prove that first and later pages both execute the provider query, but only the first page records message-query history. -- 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]
