ticdc add output old value config

ticdc/ticdc-changefeed-config.md

@@ -228,6 +228,14 @@ enable-partition-separator = true
 # The default value is "json".
 # encoding-format = "json"
 
+[sink.open]
+# Whether to output the value before the row data changes. The default value is true. When it is disabled, the UPDATE event does not output the "p" field.
+# output-old-value = true
+
+[sink.debezium]
+# Whether to output the value before the row data changes. The default value is true. When it is disabled, the UPDATE event does not output the "before" field.
+# output-old-value = true
+
 # Specifies the replication consistency configurations for a changefeed when using the redo log. For more information, see https://docs.pingcap.com/tidb/stable/ticdc-sink-to-mysql#eventually-consistent-replication-in-disaster-scenarios.
 # Note: The consistency-related configuration items only take effect when the downstream is a database and the redo log feature is enabled.
 [consistent]

ticdc/ticdc-open-api-v2.md

@@ -316,6 +316,8 @@ The `sink` parameters are described as follows:
 | `transaction_atomicity` | `STRING` type. The atomicity level of the transaction. (Optional)                                                                                                                                              |
 | `only_output_updated_columns` | `BOOLEAN` type. For MQ sinks using the `canal-json` or `open-protocol` protocol, you can specify whether only output the modified columns. The default value is `false`. (Optional) |
 | `cloud_storage_config` | The storage sink configuration. (Optional) |
+| `open`                        | The Open Protocol configuration. (Optional)                                                                             |
+| `debezium`                    | The Debezium Protocol configuration. (Optional)                                                                             |
 
 `sink.column_selectors` is an array. The parameters are described as follows:
 
@@ -349,7 +351,7 @@ The `sink.csv` parameters are described as follows:
 | `partition` | `STRING` type. The target partition for dispatching events.    |
 | `topic`     | `STRING` type. The target topic for dispatching events.        |
 
-`sink.cloud_storage_config`  parameters are described as follows:
+`sink.cloud_storage_config` parameters are described as follows:
 
 | Parameter name | Description |
 |:-----------------|:---------------------------------------|
@@ -360,6 +362,18 @@ The `sink.csv` parameters are described as follows:
 | `file_cleanup_cron_spec`   | `STRING` type. The running cycle of the scheduled cleanup task, compatible with the crontab configuration, with a format of `<Second> <Minute> <Hour> <Day of the month> <Month> <Day of the week (Optional)>`. |
 | `flush_concurrency`   | `INT` type. The concurrency for uploading a single file. |
 
+`sink.open` parameters are described as follows:
+
+| Parameter name     | Description                                                                                                                                                                |
+|:-------------------|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `output_out_value` | `BOOLEAN` type. Whether to output the value before the row data changes. The default value is `true`. When it is disabled, the UPDATE event does not output the "p" field. |
+
+`sink.debezium` parameters are described as follows:
+
+| Parameter name     | Description                                                                                                                                                                   |
+|:-------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `output_out_value` | `BOOLEAN` type. Whether to output the value before the row data changes. The default value is true. When it is disabled, the UPDATE event does not output the "before" field. |
+
 ### Example
 
 The following request creates a replication task with an ID of `test5` and `sink_uri` of `blackhome://`.