* 春-云-起动-流-火箭克。

Regarding the spring-cloud-starter-stream-rocketmq 2.2.3.RELEASE version, the support for the BindingProperties#consumer#multiplex property. The multiplex property is a standard defined to support a single consumer group to subscribe to multiple topics. Is there any plan to support this property? Currently, a single consumer group can only correspond to a single topic, which will cause a lot of resource waste and is not very flexible. RocketMq itself does not support sending ordinary messages, delayed messages, sequential messages, and non-transactional messages under the same ProductGroup because it needs to be queried, so a unique ProductGroup needs to be configured separately; similarly, when a single consumer group subscribes to messages, ordinary messages, delayed messages, and transactional messages can all be the same consumer group, but sequential messages need to be processed separately using the ConsumeMessageOrderlyService because they need to ensure the sequence. Therefore, it is usually the case that sequential messages are processed by a separate consumer group. Why does spring-cloud-starter-stream-rocketmq still continue the unreasonable pattern of RocketMq-Spring (1 group corresponds to 1 topic)? Can we support this by modifying the red box in the following figure? (topic and bysql || tags)