RockteMQ-AI commented on issue #1289: URL: https://github.com/apache/rocketmq-clients/issues/1289#issuecomment-4841660927
**Issue Evaluation** Category: `type/enhancement` | Status: **Evaluated** **Feasibility:** Feasible — straightforward change **Scope:** Java client `ConsumeTask` and `MessageInterceptor` context **Compatibility:** Fully backward-compatible — adding a field to the context does not break existing interceptors. **Assessment:** The motivation is clear: when implementing `MessageInterceptor` hooks (logging, auditing, tracing), knowing the consumer group is essential for accurate identification and troubleshooting. Currently, the context passed to `doBefore()` / `doAfter()` lacks this information, forcing hook implementations to rely on external state or thread-local workarounds. This is a small, well-scoped enhancement. The implementation should: 1. Add the consumer group name to the interceptor context (likely a `Map<String, String>` or a dedicated context object). 2. Populate it from the `ConsumeTask`'s existing consumer group reference before invoking the interceptor chain. 3. Ensure the context is available in both `doBefore()` and `doAfter()` consistently. No significant concerns. Recommend proceeding with a PR. --- *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]
