herunkang2018 commented on code in PR #3708:
URL: https://github.com/apache/flink-cdc/pull/3708#discussion_r2040509250
##########
docs/content/docs/connectors/flink-sources/mysql-cdc.md:
##########
@@ -426,6 +426,19 @@ During a snapshot operation, the connector will query each
included table to pro
Experimental option, defaults to false.
</td>
</tr>
+ <tr>
+ <td>scan.read-changelog-as-append-only.enabled</td>
+ <td>optional</td>
+ <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>
+ </td>
+ </tr>
Review Comment:
Thanks for the review. The row_kind part is already in the previous code:
[Link](https://github.com/apache/flink-cdc/pull/3708/files#diff-deb263c504d47b956b105f4a1270170d36cb1dfa39e578a599aacfc08803653cR476).
The chinese doc of row_kind is missing, so added it manually.
--
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: issues-unsubscr...@flink.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
