chennaji9 opened a new issue, #11333:
URL: https://github.com/apache/rocketmq/issues/11333
### Description
Both compaction-topic example pages contain a self-contradicting
walkthrough. The create-topic command passes the order flag:
```shell
$ bin/mqadmin updateTopic -w 8 -r 8 -a +cleanup.policy=COMPACTION -n
localhost:9876 -t ctopic -o true -c DefaultCluster
```
but the sample output printed directly beneath it reports the topic as
**not** ordered:
```
TopicConfig [topicName=ctopic, ..., topicSysFlag=0, order=false,
attributes={+cleanup.policy=COMPACTION}]
```
`-o` is `updateTopic`'s order flag (`UpdateTopicSubCommand`: `new
Option("o", "order", true, "set topic's order(true|false)")`), so the command
creates `order=true`; the sample output is stale. The contradiction matters
here because the same page's first section states that compaction topics rely
on ordered delivery ("CompactionTopic relies on orderMessages to ensure
consistency") — a reader comparing the two lines cannot tell whether ordering
is actually required or already off.
Both `docs/en/Example_Compaction_Topic.md` (line 15) and
`docs/cn/Example_Compaction_Topic_cn.md` (line 16) carry the stale
`order=false`.
### Expected behavior
The sample output should match the command shown above it: `order=true`.
--
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]
