Aias00 opened a new issue, #2269: URL: https://github.com/apache/rocketmq-dashboard/issues/2269
## Problem The persisted audit page orders only by `operated_at`. The schema uses second-precision timestamps, so records written in the same second have no deterministic tie-breaker and may move across page boundaries. The filter-options endpoint also executes an unbounded grouped query across the entire audit table on every request. As audit retention grows, repeatedly opening the filter UI can issue expensive duplicate work. ## Expected behavior - Audit pages use a stable secondary order by primary key. - Filter options are cached briefly and invalidated when a new audit record is written. - The filter response remains complete for the configured retention window and does not change its API contract. ## Scope Track 1 audit-log persistence and query behavior. ## Acceptance criteria - Equal timestamps are ordered by descending ID. - Repeated filter-option reads reuse a bounded-TTL cache. - Saving an audit record invalidates the cache. - Focused repository tests cover ordering and cache invalidation. -- 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]
