RockteMQ-AI commented on issue #2283: URL: https://github.com/apache/rocketmq-dashboard/issues/2283#issuecomment-5311298959
**Issue Evaluation** Category: `enhancement` | Status: **Evaluated** **Feasibility:** Feasible **Scope:** Topic time-range query path in Studio (likely `TopicController` or related service) **Compatibility:** No breaking changes expected; adds bounds to existing query behavior This is a well-scoped performance improvement to prevent unbounded work during Topic time-range queries. The proposal to enforce a bounded time window, add per-queue Pull budgets, and return structured feedback when limits are exceeded is sound. **Assessment:** - The problem is valid: scanning every queue from start to end offset without bounds can cause excessive Pull RPCs - The proposed solution (time window bounds + per-queue budget + structured response) addresses the root cause - Related to #2117 (timestamp validation), which provides a good foundation **Recommendation:** Proceed with implementation. Consider: 1. Making the time window and per-queue budget configurable (with sensible defaults) 2. Returning clear error messages when bounds are exceeded (not just silent truncation) 3. Adding integration tests that verify the bounds are enforced --- *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]
