RockteMQ-AI commented on issue #1051: URL: https://github.com/apache/rocketmq-dashboard/issues/1051#issuecomment-5198423467
**Issue Evaluation** Category: `enhancement` | Status: **Evaluated** **Analysis:** The `RocketMQDLQProvider.resendOne` method mentioned in the issue does not exist in the current codebase. The existing DLQ implementation is in `DlqMessageServiceImpl.java`, which uses `ConsumeMessageDirectlyResult` for message replay rather than a direct `Send` call. **Assessment:** This appears to be a feature request for implementing a new DLQ resend mechanism with proper result validation. The issue describes a desired behavior: - Using Studio-owned user property keys for resend provenance - Treating non-`SEND_OK` results as failures - Adding regression test coverage **Recommendation:** - This is a valid enhancement for improving DLQ replay reliability. - Implementation would require creating a new service method or refactoring the existing DLQ handling. - The proposed approach aligns with RocketMQ best practices for message traceability. **Feasibility:** Feasible, requires new implementation. **Scope:** Backend DLQ service layer, potentially frontend Studio integration. **Compatibility:** Additive change, no breaking changes. --- *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]
