GitHub user SweetAAAAAA added a comment to the discussion: Why I can't update TopicConfig by DefaultMQAdminExt?
It appears that the method TopicConfig.setTopicMessageType is assigning the key message.type instead of +message.type to the attributes. The relevant code can be found at [TopicConfig.java:L214](https://github.com/apache/rocketmq/blob/7ab7ddd6d25a2dac37e8bac899c5a73c4de2dbcb/common/src/main/java/org/apache/rocketmq/common/TopicConfig.java#L214) and [TOPIC_MESSAGE_TYPE_ATTRIBUTE:L41](https://github.com/apache/rocketmq/blob/7ab7ddd6d25a2dac37e8bac899c5a73c4de2dbcb/common/src/main/java/org/apache/rocketmq/common/TopicAttributes.java#L41). Inside the broker, when setting the message type for a queue, the broker reads the attributes and needs to prepend a plus sign to them. The relevant code for this is at [msgTypeAttrKey:585](https://github.com/apache/rocketmq/blob/7ab7ddd6d25a2dac37e8bac899c5a73c4de2dbcb/broker/src/main/java/org/apache/rocketmq/broker/processor/AdminBrokerProcessor.java#L585). GitHub link: https://github.com/apache/rocketmq/discussions/9647#discussioncomment-14261033 ---- This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
