This is an automated email from the ASF dual-hosted git repository.
jinrongtong pushed a commit to branch new-official-website
in repository https://gitbox.apache.org/repos/asf/rocketmq-site.git
The following commit(s) were added to refs/heads/new-official-website by this
push:
new 6fbfa3887f [ISSUE #587] Update description about
enableTopicMessageTypeCheck default (#588)
6fbfa3887f is described below
commit 6fbfa3887f4e868014722ade9602d844a4510aa3
Author: Thousand_Stars <74245184+qianchen...@users.noreply.github.com>
AuthorDate: Wed Jan 17 09:44:38 2024 +0800
[ISSUE #587] Update description about enableTopicMessageTypeCheck default
(#588)
* docs: Update description about enableTopicMessageTypeCheck default
* docs: Update description about enableTopicMessageTypeCheck default
---
.../version-5.0/01-introduction/02concepts.md | 2 +-
.../version-5.0/03-domainModel/02topic.md | 2 +-
versioned_docs/version-5.0/01-introduction/02concepts.md | 2 +-
versioned_docs/version-5.0/03-domainModel/02topic.md | 6 +++---
4 files changed, 6 insertions(+), 6 deletions(-)
diff --git
a/i18n/en/docusaurus-plugin-content-docs/version-5.0/01-introduction/02concepts.md
b/i18n/en/docusaurus-plugin-content-docs/version-5.0/01-introduction/02concepts.md
index 0976315933..3d99f8b671 100644
---
a/i18n/en/docusaurus-plugin-content-docs/version-5.0/01-introduction/02concepts.md
+++
b/i18n/en/docusaurus-plugin-content-docs/version-5.0/01-introduction/02concepts.md
@@ -11,7 +11,7 @@ Categories defined by message transfer characteristics for
type management and s
:::info
-Starting from version 5.0, Apache RocketMQ supports enforcing the validation
of message types, that is, each topic only allows messages of a single type to
be sent. This can better facilitate operation and management of production
systems and avoid confusion. However, to ensure backward compatibility with
version 4.x, the validation feature is disabled by default. It is recommended
to enable it manually through the server parameter
"enableTopicMessageTypeCheck".
+Starting from version 5.0, Apache RocketMQ supports enforcing the validation
of message types, that is, each topic only allows messages of a single type to
be sent. This can better facilitate operation and management of production
systems and avoid confusion. However, to ensure backward compatibility with
version 4.x, the validation feature is enable by default.
:::
## MessageQueue
diff --git
a/i18n/en/docusaurus-plugin-content-docs/version-5.0/03-domainModel/02topic.md
b/i18n/en/docusaurus-plugin-content-docs/version-5.0/03-domainModel/02topic.md
index 28e941dc75..73bdf0d9f1 100644
---
a/i18n/en/docusaurus-plugin-content-docs/version-5.0/03-domainModel/02topic.md
+++
b/i18n/en/docusaurus-plugin-content-docs/version-5.0/03-domainModel/02topic.md
@@ -59,7 +59,7 @@ A topic contains one or more queues. Message storage and
scalability are impleme
* Transaction: [Transaction
messages](../04-featureBehavior/04transactionmessage.md). Apache RocketMQ
supports distributed transaction messages and ensures transaction consistency
of database updates and message calls.
-* Constraint: Starting from version 5.0, Apache RocketMQ supports enforcing
the validation of message types, that is, each topic only allows messages of a
single type to be sent. This can better facilitate operation and management of
production systems and avoid confusion. However, to ensure backward
compatibility with version 4.x, the validation feature is disabled by default.
It is recommended to enable it manually through the server parameter
"enableTopicMessageTypeCheck".
+* Constraint: Starting from version 5.0, Apache RocketMQ supports enforcing
the validation of message types, that is, each topic only allows messages of a
single type to be sent. This can better facilitate operation and management of
production systems and avoid confusion. However, to ensure backward
compatibility with version 4.x, the validation feature is enable by default.
## Behavior constraints
diff --git a/versioned_docs/version-5.0/01-introduction/02concepts.md
b/versioned_docs/version-5.0/01-introduction/02concepts.md
index d0dcecd2b0..59ab60928b 100644
--- a/versioned_docs/version-5.0/01-introduction/02concepts.md
+++ b/versioned_docs/version-5.0/01-introduction/02concepts.md
@@ -10,7 +10,7 @@ Apache RocketMQ 中按照消息传输特性的不同而定义的分类，用于
:::info
-Apache RocketMQ
从5.0版本开始，支持强制校验消息类型，即每个主题Topic只允许发送一种消息类型的消息，这样可以更好的运维和管理生产系统，避免混乱。但同时保证向下兼容4.x版本行为，强制校验功能默认关闭，推荐通过服务端参数
enableTopicMessageTypeCheck 手动开启校验。
+Apache RocketMQ
从5.0版本开始，支持强制校验消息类型，即每个主题Topic只允许发送一种消息类型的消息，这样可以更好的运维和管理生产系统，避免混乱。但同时保证向下兼容4.x版本行为，强制校验功能默认开启。
:::
diff --git a/versioned_docs/version-5.0/03-domainModel/02topic.md
b/versioned_docs/version-5.0/03-domainModel/02topic.md
index 0be00e9e60..13d5bfcf46 100644
--- a/versioned_docs/version-5.0/03-domainModel/02topic.md
+++ b/versioned_docs/version-5.0/03-domainModel/02topic.md
@@ -59,7 +59,7 @@
* Transaction：[事务消息](../04-featureBehavior/04transactionmessage.md)，Apache
RocketMQ 支持分布式事务消息，支持应用数据库更新和消息调用的事务一致性保障。
-* 约束：Apache RocketMQ
从5.0版本开始，支持强制校验消息类型，即每个主题只允许发送一种消息类型的消息，这样可以更好的运维和管理生产系统，避免混乱。为保证向下兼容4.x版本行为，强制校验功能默认关闭，推荐通过服务端参数
enableTopicMessageTypeCheck 开启校验。
+* 约束：Apache RocketMQ
从5.0版本开始，支持强制校验消息类型，即每个主题只允许发送一种消息类型的消息，这样可以更好的运维和管理生产系统，避免混乱。为保证向下兼容4.x版本行为，强制校验功能默认开启。
@@ -77,7 +77,7 @@ Apache RocketMQ 5.x版本支持将消息类型拆分到主题中进行独立运
:::info
-为保证向下兼容4.x版本行为，上述强制校验功能默认关闭，推荐通过服务端参数 enableTopicMessageTypeCheck 开启校验。
+为保证向下兼容4.x版本行为，上述强制校验功能默认开启。
:::
@@ -91,7 +91,7 @@ Apache RocketMQ 5.x版本支持将消息类型拆分到主题中进行独立运
## 版本兼容性
-消息类型的强制校验，仅 Apache RocketMQ 服务端5.x版本支持，且默认关闭，推荐部署时打开配置。 Apache RocketMQ
服务端4.x和3.x历史版本的SDK不支持强制校验，您需要自己保证消息类型一致。 如果您使用的服务端版本为历史版本，建议您升级到
+消息类型的强制校验，仅 Apache RocketMQ 服务端5.x版本支持，且默认开启，推荐部署时打开配置。 Apache RocketMQ
服务端4.x和3.x历史版本的SDK不支持强制校验，您需要自己保证消息类型一致。 如果您使用的服务端版本为历史版本，建议您升级到
Apache RocketMQ 服务端5.x版本。
## 使用示例
