X-LightYear opened a new issue, #5110: URL: https://github.com/apache/rocketmq-dashboard/issues/5110
## Problem The Aliyun `ListConsumerGroups` response exposes `topicName` for Lite consumer groups, but the Studio Aliyun converter drops this field. The resulting `ConsumerGroupVO.subscribedTopics` is empty even though the cloud API identifies the LiteTopic subscription. ## Reproduction 1. Use an Aliyun RocketMQ instance with a Lite consumer group. 2. The `ListConsumerGroups` response contains `messageModel: LITE_SELECTIVE` and `topicName: lite-session-a`. 3. Load consumer groups through `AliyunInstanceProvider.listConsumerGroups`. A deterministic regression test on current `rocketmq-studio` reproduces the behavior: `AliyunInstanceProviderTest.listConsumerGroupsShouldPreserveLiteConsumerTopicTest` ## Expected behavior The returned `ConsumerGroupVO` should preserve the Lite consumer group's topic in `subscribedTopics`, so downstream group inventory and MCP projections retain the subscription identity. ## Actual behavior `subscribedTopics` is empty because `AliyunConverters.toConsumerGroupVO` maps group metadata but never maps the response `topicName` field. ## Root cause Alibaba Cloud documents `topicName` as the name of the topic for a Lite consumer group in `ListConsumerGroups`: https://help.aliyun.com/en/apsaramq-for-rocketmq/cloud-message-queue-rocketmq-5-x-series/developer-reference/api-rocketmq-2022-08-01-listconsumergroups The converter ignores that documented field, so the loss occurs at the provider-to-Studio VO boundary. ## Scope This is a narrow Aliyun provider mapping fix. Normal consumer groups without `topicName` should continue to expose an empty topic list. It is unrelated to the existing LiteTopic lag-row issue. -- 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]
