RockteMQ-AI commented on PR #4267: URL: https://github.com/apache/rocketmq-dashboard/pull/4267#issuecomment-5658822450
**Issue Evaluation** Category: `enhancement` | Status: **Evaluated** **Feasibility:** Feasible **Scope:** `MessageRecordVO`, `RocketMQMessageProvider.toRecordVO`, `MessageDetailViewDialog.jsx` **Compatibility:** No breaking changes — additive fields with graceful fallback. Well-structured request. Exposing `brokerName`, `queueId`, and `queueOffset` in the message detail panel fills a clear operational gap: these fields are essential for locating where a message physically resides in the store, and they are already available on `MessageExt` / `SelectMappedBufferResult`. The single-point mapping in `toRecordVO` again ensures all query paths (by Topic/Key/msgId/queue browse) benefit from the change. The frontend placement after "Message ID" in the Descriptions group is logical — storage location is core identity metadata. The caveat about cloud providers not populating these fields is handled consistently with existing optional fields (fallback to `-`). Clean, low-risk enhancement. Together with #4271 and #4269, this forms a coherent "message metadata completeness" improvement set. --- *Automated evaluation by github-manager* -- 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]
