rocketmq-v5-client-spring-boot怎么没有rocketmq.push-consumer配置了？

[JogJo]

application.yml中配置，只有producer和simple-consumer，没有看到push-consumer，是取消掉了吗？

官方示例里还是使用了push-consumer去配置，并通过实现RocketMQListener来消费消息

rocketmq:
push-consumer:
endpoints: 192.168.1.100:8081
tag: "*"
simple-consumer:
endpoints: 192.168.1.100:8081

[freedom0123]

RocketMQProperties 里面没有 Push-consumer 的配置了，代码里面，实际上在 构建 DefaultListenerContainer 时

private DefaultListenerContainer createRocketMQListenerContainer(String name, Object bean, RocketMQMessageListener annotation) {
        DefaultListenerContainer container = new DefaultListenerContainer();
        container.setName(name);
        container.setRocketMQMessageListener(annotation);
        container.setMessageListener((RocketMQListener) bean);
        container.setAccessKey(environment.resolvePlaceholders(annotation.accessKey()));
        container.setSecretKey(environment.resolvePlaceholders(annotation.secretKey()));
        container.setConsumerGroup(environment.resolvePlaceholders(annotation.consumerGroup()));
        container.setTag(environment.resolvePlaceholders(annotation.tag()));
        // 这里 
        container.setEndpoints(environment.resolvePlaceholders(annotation.endpoints()));
        container.setTopic(environment.resolvePlaceholders(annotation.topic()));
        container.setNamespace(environment.resolvePlaceholders(annotation.namespace()));
        container.setRequestTimeout(Duration.ofSeconds(annotation.requestTimeout()));
        container.setMaxCachedMessageCount(annotation.maxCachedMessageCount());
        container.setConsumptionThreadCount(annotation.consumptionThreadCount());
        container.setMaxCacheMessageSizeInBytes(annotation.maxCacheMessageSizeInBytes());
        container.setType(annotation.filterExpressionType());
        return container;
    }

通过这种方式，从配置文件之中获取的

String ENDPOINTS_PLACEHOLDER = "${rocketmq.push-consumer.endpoints:}"; 

我理解是没有取消， 但是为什么不直接放在 RocketMQProperties 之中呢？

[chathoward712-cpu]

现在是通过注解上的配置 @RocketMQMessageListener(topic = "demo-topic", consumerGroup = "demo-group")
可以将上面的demo-topic配置到application.yml 获取
@RocketMQMessageListener(
topic = "${rocketmq.consumer.demo-topic}",
consumerGroup = "${rocketmq.consumer.demo-group}"
)

application.yml
rocketmq:
consumer:
demo-topic: demo-topic-from-yml
demo-group: demo-group-from-yml

[RockteMQ-AI]

Issue Evaluation

Category: question

The rocketmq-v5-client-spring-boot starter currently supports producer and simple-consumer configurations. The push-consumer configuration may not yet be available in the v5 starter.

Workaround: You can use the simple-consumer with a polling loop, or use the v4-style rocketmq-spring-boot-starter which still supports push-consumer via @RocketMQMessageListener.

Check the official samples for the latest supported configuration patterns.

---

Automated evaluation by RockteMQ-AI

[RockteMQ-AI]

Issue Evaluation\n\nCategory: question | Status: Needs Clarification\n\nThis appears to be a usage question or configuration issue. Please provide:\n- RocketMQ Spring version\n- Configuration details\n- Error logs or stack traces if applicable\n\nFor usage questions, consider checking the documentation or asking in GitHub Discussions.\n\n---\nAutomated evaluation by github-manager

[RockteMQ-AI]

Issue Evaluation

Category: question

In rocketmq-v5-client-spring-boot, the push consumer configuration model changed. The old rocketmq.push-consumer.* properties are replaced by the v5 unified configuration:

rocketmq.consumer.endpoints=<your-proxy-endpoint>
rocketmq.consumer.consumer-group=<your-group>
rocketmq.consumer.topic=<your-topic>

The v5 client unifies push and pull patterns. Check the v5 migration guide for the complete mapping.

---

Automated evaluation by RockteMQ-AI