Re: [D] the expected type is FIFO, but actual type is NORMAL BROKER [rocketmq-clients]

GitHub user jevonsnotes added a comment to the discussion: the expected type is FIFO, but actual type is NORMAL BROKER > > 我按照您的说法增加了 __SHARDINGKEY 确实可以收发消息了，但是这个分布式键属性的意义和作用是什么呢 > > 为了保证同一个 ShardingKey 的消息发送到相同队列上 > > > 我使用的是rocketmq spring进行发送的消息 > > 新出了一个版本 > [rocketmq-v5-client-spring-b

Re: [D] the expected type is FIFO, but actual type is NORMAL BROKER [rocketmq-clients]

GitHub user Gonzo-Tan added a comment to the discussion: the expected type is FIFO, but actual type is NORMAL BROKER > > > 我按照您的说法增加了 __SHARDINGKEY 确实可以收发消息了，但是这个分布式键属性的意义和作用是什么呢 > > > > > > 为了保证同一个 ShardingKey 的消息发送到相同队列上 > > > 我使用的是rocketmq spring进行发送的消息 > > > > > > 新出了一个版本 > > [rocketmq

Re: [D] the expected type is FIFO, but actual type is NORMAL BROKER [rocketmq-clients]

GitHub user jevonsnotes added a comment to the discussion: the expected type is FIFO, but actual type is NORMAL BROKER 好的，我尝试一下，谢谢 GitHub link: https://github.com/apache/rocketmq-clients/discussions/785#discussioncomment-9967280 This is an automatically sent email for dev@rocketmq.apach

[I] Building ARM version image, script execution failed [rocketmq-docker]

MagicGopher opened a new issue, #107: URL: https://github.com/apache/rocketmq-docker/issues/107 Problem description. The build script execution failed, and the terminal information is as follows: ``` > sh build-image.sh 4.9.8 centos Version = 4.9.8 DEPRECATED: The legacy build

Re: [D] rocketmq 5.x support msg trace，just like 4.x [rocketmq]

GitHub user onejimmyboy added a comment to the discussion: rocketmq 5.x support msg trace，just like 4.x 请问您也使用的是proxy模式吗?又找到方法吗？ GitHub link: https://github.com/apache/rocketmq/discussions/8026#discussioncomment-9973317 This is an automatically sent email for dev@rocketmq.apache.org. T