This is an automated email from the ASF dual-hosted git repository.
yux pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/flink-cdc.git
The following commit(s) were added to refs/heads/master by this push:
new f6197d223 [FLINK-37738][docs] Fix Postgres Chinese and English
document contents (#4109)
f6197d223 is described below
commit f6197d223fdc4710200e9e54b69ff3a57d2202f9
Author: ouyangwulin <mr.art...@gmail.com>
AuthorDate: Tue Aug 26 11:25:12 2025 +0800
[FLINK-37738][docs] Fix Postgres Chinese and English document contents
(#4109)
---
docs/content.zh/docs/connectors/flink-sources/postgres-cdc.md | 10 +++++-----
docs/content/docs/connectors/flink-sources/postgres-cdc.md | 10 +++++-----
2 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/docs/content.zh/docs/connectors/flink-sources/postgres-cdc.md
b/docs/content.zh/docs/connectors/flink-sources/postgres-cdc.md
index 557e1d697..1470f7453 100644
--- a/docs/content.zh/docs/connectors/flink-sources/postgres-cdc.md
+++ b/docs/content.zh/docs/connectors/flink-sources/postgres-cdc.md
@@ -273,11 +273,11 @@ Connector Options
<td style="word-wrap: break-word;">false</td>
<td>Boolean</td>
<td>
- Whether to convert the changelog stream to an append-only stream.<br>
- This feature is only used in special scenarios where you need to save
upstream table deletion messages. For example, in a logical deletion scenario,
users are not allowed to physically delete downstream messages. In this case,
this feature is used in conjunction with the row_kind metadata field.
Therefore, the downstream can save all detailed data at first, and then use the
row_kind field to determine whether to perform logical deletion.<br>
- The option values are as follows:<br>
- <li>true: All types of messages (including INSERT, DELETE,
UPDATE_BEFORE, and UPDATE_AFTER) will be converted into INSERT messages.</li>
- <li>false (default): All types of messages are sent as is.</li>
+ 是否将 changelog 数据流转换为 append-only 数据流。<br>
+ 仅在需要保存上游表删除消息等特殊场景下开启使用，比如在逻辑删除场景下，用户不允许物理删除下游消息，此时使用该特性，并配合 row_kind
元数据字段，下游可以先保存所有明细数据，再通过 row_kind 字段判断是否进行逻辑删除。<br>
+ 参数取值如下：<br>
+ <li>true：所有类型的消息（包括INSERT、DELETE、UPDATE_BEFORE、UPDATE_AFTER）都会转换成
INSERT 类型的消息。</li>
+ <li>false（默认）：所有类型的消息都保持原样下发。</li>
</td>
</tr>
</tbody>
diff --git a/docs/content/docs/connectors/flink-sources/postgres-cdc.md
b/docs/content/docs/connectors/flink-sources/postgres-cdc.md
index 11b0a275f..de1341c7b 100644
--- a/docs/content/docs/connectors/flink-sources/postgres-cdc.md
+++ b/docs/content/docs/connectors/flink-sources/postgres-cdc.md
@@ -270,11 +270,11 @@ SELECT * FROM shipments;
<td style="word-wrap: break-word;">false</td>
<td>Boolean</td>
<td>
- 是否将 changelog 数据流转换为 append-only 数据流。<br>
- 仅在需要保存上游表删除消息等特殊场景下开启使用，比如在逻辑删除场景下，用户不允许物理删除下游消息，此时使用该特性，并配合 row_kind
元数据字段，下游可以先保存所有明细数据，再通过 row_kind 字段判断是否进行逻辑删除。<br>
- 参数取值如下：<br>
- <li>true：所有类型的消息（包括INSERT、DELETE、UPDATE_BEFORE、UPDATE_AFTER）都会转换成
INSERT 类型的消息。</li>
- <li>false（默认）：所有类型的消息都保持原样下发。</li>
+ Whether to convert the changelog stream to an append-only stream.<br>
+ This feature is only used in special scenarios where you need to save
upstream table deletion messages. For example, in a logical deletion scenario,
users are not allowed to physically delete downstream messages. In this case,
this feature is used in conjunction with the row_kind metadata field.
Therefore, the downstream can save all detailed data at first, and then use the
row_kind field to determine whether to perform logical deletion.<br>
+ The option values are as follows:<br>
+ <li>true: All types of messages (including INSERT, DELETE,
UPDATE_BEFORE, and UPDATE_AFTER) will be converted into INSERT messages.</li>
+ <li>false (default): All types of messages are sent as is.</li>
</td>
</tr>
</tbody>
