Skip to content

Commit a34ab52

Browse files
committed
Update zh file accordingly and modify text format
1 parent f68defc commit a34ab52

File tree

2 files changed

+13
-7
lines changed

2 files changed

+13
-7
lines changed

en_US/data-integration/data-bridge-rabbitmq.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -161,20 +161,20 @@ This section demonstrates how to create a rule in the Dashboard for processing m
161161

162162
* **Exchange**: Enter `test_exchange` created before, which means messages will be published to this exchange.
163163

164-
::: tip
164+
::: tip Note
165165

166-
**Note**: Make sure the **Exchange** has been created in RabbitMQ, otherwise the action will be temporarily broken and periodically try to re-create the connection.
166+
Make sure the exchange has been created in RabbitMQ, otherwise the action will be temporarily broken and periodically try to re-create the connection.
167167
:::
168168

169169
* **Routing Key**: Enter `test_routing_key` created before, which is the RabbitMQ routing key for publishing messages.
170170

171171
::: tip
172172

173-
The **Exchange** and **Routing Key** can be configured as template values, enabling dynamic routing using placeholders to extract values from incoming MQTT message payloads.
173+
The exchange and routing key can be configured as template values, enabling dynamic routing using placeholders to extract values from incoming MQTT message payloads.
174174

175-
For example, to dynamically set the **Routing Key** based on a field in the payload, configure the **Routing Key** as `${payload.akey}`. This extracts the `akey` field from the payload and uses its value as the routing key.
175+
For example, to dynamically set the routing Key based on a field in the payload, configure the routing key as `${payload.akey}`. This extracts the `akey` field from the payload and uses its value as the routing key.
176176

177-
**Note**: In batch mode, the **Exchange** and **Routing Key** template values must remain constant for all messages in the batch. This ensures consistent routing and avoids conflicts during batch processing.
177+
**Note**: In batch mode, the exchange and routing key template values must remain constant for all messages in the batch. This ensures consistent routing and avoids conflicts during batch processing.
178178
:::
179179

180180
* **Virtual Host**: Enter RabbitMQ virtual host; `/` by default.

zh_CN/data-integration/data-bridge-rabbitmq.md

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -157,13 +157,19 @@ docker run -it --rm --name rabbitmq -p 127.0.0.1:5672:5672 -p 127.0.0.1:15672:15
157157

158158
* **交换机**: 输入之前创建的 `test_exchange`, 消息将被发送到该交换机。
159159

160+
::: tip 注意
161+
162+
请确保交换机已在 RabbitMQ 中创建,否则该动作将暂时失败,并周期性地尝试重新创建连接。
163+
164+
:::
165+
160166
* **路由键**: 输入之前创建的 `test_routing_key`,用于将消息路由到 RabbitMQ 交换中的正确队列。
161167

162168
::: tip
163169

164-
**交换机****路由健**支持配置为模板值,可以使用占位符从接收到的 MQTT 消息 payload 中提取值,从而实现动态路由。例如,可以根据 payload 中的某个字段动态设置**路由健**,将其配置为 `${payload.akey}`,从 payload 中提取 `akey` 字段的值并作为路由键。
170+
交换机和路由健支持配置为模板值,可以使用占位符从接收到的 MQTT 消息 payload 中提取值,从而实现动态路由。例如,可以根据 payload 中的某个字段动态设置路由健,将其配置为 `${payload.akey}`,从 payload 中提取 `akey` 字段的值并作为路由键。
165171

166-
**注意**:在批量模式下,**交换机****路由健**的模板值必须在批次中的所有消息中保持一致,以确保路由的统一性并避免批处理过程中出现冲突。
172+
**注意**:在批量模式下,交换机和路由健的模板值必须在批次中的所有消息中保持一致,以确保路由的统一性并避免批处理过程中出现冲突。
167173

168174
:::
169175

0 commit comments

Comments
 (0)