ticdc: Fix some ticdc docs master 6.5 (#13664)

ticdc/ticdc-changefeed-config.md

@@ -84,22 +84,22 @@ rules = ['*.*', '!test.*']
 # IgnoreTxnStartTs = []
 
 # Event filter rules.
-# The detailed syntax is described in the event filter rules section.
+# The detailed syntax is described in <https://docs.pingcap.com/tidb/stable/ticdc-filter>
 # The first event filter rule.
-[[filter.event-filters]]
-matcher = ["test.worker"] # matcher is an allow list, which means this rule only applies to the worker table in the test database.
-ignore-event = ["insert"] # Ignore insert events.
-ignore-sql = ["^drop", "add column"] # Ignore DDLs that start with "drop" or contain "add column".
-ignore-delete-value-expr = "name = 'john'" # Ignore delete DMLs that contain the condition "name = 'john'".
-ignore-insert-value-expr = "id >= 100" # Ignore insert DMLs that contain the condition "id >= 100".
-ignore-update-old-value-expr = "age < 18" # Ignore update DMLs whose old value contains "age < 18".
-ignore-update-new-value-expr = "gender = 'male'" # Ignore update DMLs whose new value contains "gender = 'male'".
+# [[filter.event-filters]]
+# matcher = ["test.worker"] # matcher is an allow list, which means this rule only applies to the worker table in the test database.
+# ignore-event = ["insert"] # Ignore insert events.
+# ignore-sql = ["^drop", "add column"] # Ignore DDLs that start with "drop" or contain "add column".
+# ignore-delete-value-expr = "name = 'john'" # Ignore delete DMLs that contain the condition "name = 'john'".
+# ignore-insert-value-expr = "id >= 100" # Ignore insert DMLs that contain the condition "id >= 100".
+# ignore-update-old-value-expr = "age < 18" # Ignore update DMLs whose old value contains "age < 18".
+# ignore-update-new-value-expr = "gender = 'male'" # Ignore update DMLs whose new value contains "gender = 'male'".
 
 # The second event filter rule.
-matcher = ["test.fruit"] # matcher is an allow list, which means this rule only applies to the fruit table in the test database.
-ignore-event = ["drop table"] # Ignore drop table events.
-ignore-sql = ["delete"] # Ignore delete DMLs.
-ignore-insert-value-expr = "price > 1000 and origin = 'no where'" # Ignore insert DMLs that contain the conditions "price > 1000" and "origin = 'no where'".
+# matcher = ["test.fruit"] # matcher is an allow list, which means this rule only applies to the fruit table in the test database.
+# ignore-event = ["drop table", "delete"] # Ignore the `drop table` DDL events and the `delete` DML events.
+# ignore-sql = ["^drop table", "alter table"] # Ignore DDL statements that start with `drop table` or contain `alter table`.
+# ignore-insert-value-expr = "price > 1000 and origin = 'no where'" # Ignore insert DMLs that contain the conditions "price > 1000" and "origin = 'no where'".
 
 [scheduler]
 # Splits a table into multiple replication ranges based on the number of Regions, and these ranges can be replicated by multiple TiCDC nodes.
@@ -122,31 +122,31 @@ write-key-threshold = 0
 # Since v6.1.0, TiDB supports two types of event dispatchers: partition and topic. For more information, see <partition and topic link>.
 # The matching syntax of matcher is the same as the filter rule syntax. For details about the matcher rules, see <>.
 # Note: This configuration item only takes effect if the downstream is MQ.
-dispatchers = [
-    {matcher = ['test1.*', 'test2.*'], topic = "Topic expression 1", partition = "ts" },
-    {matcher = ['test3.*', 'test4.*'], topic = "Topic expression 2", partition = "index-value" },
-    {matcher = ['test1.*', 'test5.*'], topic = "Topic expression 3", partition = "table"},
-    {matcher = ['test6.*'], partition = "ts"}
-]
+# dispatchers = [
+#     {matcher = ['test1.*', 'test2.*'], topic = "Topic expression 1", partition = "ts" },
+#     {matcher = ['test3.*', 'test4.*'], topic = "Topic expression 2", partition = "index-value" },
+#     {matcher = ['test1.*', 'test5.*'], topic = "Topic expression 3", partition = "table"},
+#     {matcher = ['test6.*'], partition = "ts"}
+# ]
 
 # The protocol configuration item specifies the protocol format of the messages sent to the downstream.
 # When the downstream is Kafka, the protocol can only be canal-json or avro.
 # When the downstream is a storage service, the protocol can only be canal-json or csv.
 # Note: This configuration item only takes effect if the downstream is Kafka or a storage service.
-protocol = "canal-json"
+# protocol = "canal-json"
 
 # The following three configuration items are only used when you replicate data to storage sinks and can be ignored when replicating data to MQ or MySQL sinks.
 # Row terminator, used for separating two data change events. The default value is an empty string, which means "\r\n" is used.
-terminator = ''
-# Date separator type used in the file directory. Value options are `none`, `year`, `month`, and `day`. `none` is the default value and means that the date is not separated. For more information, see <https://docs.pingcap.com/tidb/dev/ticdc-sink-to-cloud-storage#data-change-records>. 
+# terminator = ''
+# Date separator type used in the file directory. Value options are `none`, `year`, `month`, and `day`. `none` is the default value and means that the date is not separated. For more information, see <https://docs.pingcap.com/tidb/dev/ticdc-sink-to-cloud-storage#data-change-records>.
 # Note: This configuration item only takes effect if the downstream is a storage service.
 date-separator = 'none'
-# Whether to use partitions as the separation string. The default value is true, which means that partitions in a table are stored in separate directories. It is recommended that you keep the value as `true` to avoid potential data loss in downstream partitioned tables <https://github.com/pingcap/tiflow/issues/8724>. For usage examples, see <https://docs.pingcap.com/tidb/dev/ticdc-sink-to-cloud-storage#data-change-records)>. 
+# Whether to use partitions as the separation string. The default value is true, which means that partitions in a table are stored in separate directories. It is recommended that you keep the value as `true` to avoid potential data loss in downstream partitioned tables <https://github.com/pingcap/tiflow/issues/8724>. For usage examples, see <https://docs.pingcap.com/tidb/dev/ticdc-sink-to-cloud-storage#data-change-records)>.
 # Note: This configuration item only takes effect if the downstream is a storage service.
 enable-partition-separator = true
 
-# Schema registry URL. 
-# Note: This configuration item only takes effect if the downstream is MQ. 
+# Schema registry URL.
+# Note: This configuration item only takes effect if the downstream is MQ.
 # schema-registry = "http://localhost:80801/subjects/{subject-name}/versions/{version-number}/schema"
 
 # Specifies the number of encoder threads used when encoding data.
@@ -165,17 +165,17 @@ enable-partition-separator = true
 # only-output-updated-columns = false
 
 # Since v6.5.0, TiCDC supports saving data changes to storage services in CSV format. Ignore the following configurations if you replicate data to MQ or MySQL sinks.
-[sink.csv]
+# [sink.csv]
 # The character used to separate fields in the CSV file. The value must be an ASCII character and defaults to `,`.
-delimiter = ','
+# delimiter = ','
 # The quotation character used to surround fields in the CSV file. The default value is `"`. If the value is empty, no quotation is used.
-quote = '"'
+# quote = '"'
 # The character displayed when a CSV column is null. The default value is `\N`.
-null = '\N'
+# null = '\N'
 # Whether to include commit-ts in CSV rows. The default value is false.
-include-commit-ts = false
+# include-commit-ts = false
 
-# 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. 
+# 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.
 [sink.consistent]
 # The data consistency level. Available options are "none" and "eventual". "none" means that the redo log is disabled.