From fec86a1a8993661075c35604e9a16fae94807cb2 Mon Sep 17 00:00:00 2001 From: Ti Chi Robot Date: Mon, 29 Jul 2024 13:38:47 +0800 Subject: [PATCH] ticdc-faq: fix typo for commitTS (#18382) (#18384) --- ticdc/ticdc-faq.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ticdc/ticdc-faq.md b/ticdc/ticdc-faq.md index b6c863cf40d71..9881de0f492cf 100644 --- a/ticdc/ticdc-faq.md +++ b/ticdc/ticdc-faq.md @@ -282,9 +282,9 @@ For TiCDC versions earlier than v6.5.2, it is recommended that you deploy TiCDC Currently, TiCDC adopts the following order: -1. TiCDC blocks the replication progress of the tables affected by DDL statements until the DDL `CommiTs`. This ensures that DML statements executed before DDL `CommiTs` can be successfully replicated to the downstream first. +1. TiCDC blocks the replication progress of the tables affected by DDL statements until the DDL `commitTS`. This ensures that DML statements executed before DDL `commitTS` can be successfully replicated to the downstream first. 2. TiCDC continues with the replication of DDL statements. If there are multiple DDL statements, TiCDC replicates them in a serial manner. -3. After the DDL statements are executed in the downstream, TiCDC will continue with the replication of DML statements executed after DDL `CommiTs`. +3. After the DDL statements are executed in the downstream, TiCDC will continue with the replication of DML statements executed after DDL `commitTS`. ## How should I check whether the upstream and downstream data is consistent?