RockteMQ-AI commented on issue #3163: URL: https://github.com/apache/rocketmq-dashboard/issues/3163#issuecomment-5544528742
**Issue Evaluation** Category: `enhancement` | Status: **Evaluated** Thank you for the detailed report. This is a valid UI/UX gap — the backend already accepts `startTime`, `endTime`, and `tag` for key queries, but the frontend only exposes Topic and Message Key fields in that mode. **Assessment:** - **Feasibility:** Feasible — the backend API contract already supports these parameters; the change is primarily frontend (Vue) to render the date range picker and tag input in Message Key mode, and to include those fields in the query payload. - **Scope:** Message query page (`message` component), query normalizer, and the backend key-query validation path (to enforce the same time-window checks as topic queries). - **Compatibility:** No breaking changes — additive UI exposure of existing API parameters. Message ID lookups remain unaffected as point lookups. **Suggested approach:** 1. Extend the Message Key query form to include the date range picker and optional tag input (same components used in Topic mode). 2. Ensure the query normalizer passes `startTime`, `endTime`, and `tag` through for key queries. 3. Apply consistent time-window validation on the backend for key queries (start < end, non-negative, ≤ 7 days), while keeping Message ID lookups exempt. 4. Update query history replay to preserve key-query time window and tag. This is a good candidate for a community contribution. --- *Automated evaluation by RockteMQ-AI* -- 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]
