RockteMQ-AI commented on issue #4843: URL: https://github.com/apache/rocketmq-dashboard/issues/4843#issuecomment-5771042174
**Issue Evaluation** Category: `bug` | Status: **Confirmed** The reported issue has been verified against the current codebase. **Root Cause:** In `AliyunConverters.toTopicType()`, the mapping from Aliyun message type strings to `TopicType` has no case for "LITE". The `default` branch falls through to `TopicType.NORMAL` (line 151), with a comment noting "Unknown message types fall back to NORMAL so read paths..." This means Aliyun lite topics are incorrectly reported as NORMAL in the console. Meanwhile, `RocketMQLiteTopicProvider` correctly identifies lite topics via `TopicMessageType.LITE.equals(config.getTopicMessageType())` at line 369, confirming the system knows about the LITE type — but the Aliyun converter does not map it. **Impact:** Lite topics in Aliyun instances display as NORMAL in the dashboard, misleading users about topic behavior and configuration. **Severity:** Medium — display/metadata issue, does not affect message routing. **Suggested fix:** Add a `case "LITE"` in `AliyunConverters.toTopicType()` that maps to the appropriate `TopicType.LITE` (or equivalent). An automated fix proposal can be generated. Reply `/approve` to proceed with PR generation. --- *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]
