changed github.com/pingcap/ticdc to github.com/pingcap/tiflow (#857)

Author: hfxsd

Diff for: en/_index.md

@@ -6,11 +6,11 @@ aliases: ['/docs/tidb-data-migration/dev/']
 
 # TiDB Data Migration Documentation
 
-[TiDB Data Migration](https://github.com/pingcap/ticdc/tree/master/dm) (DM) is a convenient data migration tool, which supports data migration from MySQL-compatible databases (such as MySQL, MariaDB, and Aurora MySQL) into TiDB. It can help to reduce the operation cost of data migration.
+[TiDB Data Migration](https://github.com/pingcap/tiflow/tree/master/dm) (DM) is a convenient data migration tool, which supports data migration from MySQL-compatible databases (such as MySQL, MariaDB, and Aurora MySQL) into TiDB. It can help to reduce the operation cost of data migration.
 
 > **Note:**
 >
-> - Since October 2021, DM's GitHub repository has been moved to [pingcap/ticdc](https://github.com/pingcap/ticdc/tree/master/dm). If you see any issues with DM, submit your issue to the `pingcap/ticdc` repository for feedback.
+> - Since December 2021, DM's GitHub repository has been moved to [pingcap/tiflow](https://github.com/pingcap/tiflow/tree/master/dm). If you see any issues with DM, submit your issue to the `pingcap/tiflow` repository for feedback.
 > - In earlier versions (v1.0 and v2.0), DM uses version numbers that are independent of TiDB. Since v5.3, DM uses the same version number as TiDB. The next version of DM v2.0 is DM v5.3. There are no compatibility changes from DM v2.0 to v5.3, and the upgrade process is no different from a normal upgrade, only an increase in version number.
 
 <NavColumns>

Diff for: en/deploy-a-dm-cluster-using-binary.md

@@ -22,7 +22,7 @@ Download the official binary using the download link in the following table:
 
 > **Note:**
 >
-> `{version}` in the above download link indicates the version number of TiDB. For example, the download link for `v1.0.1` is `https://download.pingcap.org/dm-v1.0.1-linux-amd64.tar.gz`. You can check the published DM versions in the [DM Release](https://github.com/pingcap/ticdc/releases) page.
+> `{version}` in the above download link indicates the version number of TiDB. For example, the download link for `v1.0.1` is `https://download.pingcap.org/dm-v1.0.1-linux-amd64.tar.gz`. You can check the published DM versions in the [DM Release](https://github.com/pingcap/tiflow/releases) page.
 
 The downloaded files have two subdirectories, `bin` and `conf`. The `bin` directory contains the binary files of DM-master, DM-worker, and dmctl. The `conf` directory contains the sample configuration files.
 

Diff for: en/faq.md

@@ -153,7 +153,7 @@ In DM 1.0, you need to enable `enable-heartbeat` to generate the monitor data. I
 
 ## How to handle the error `fail to initial unit Sync of subtask` when DM is starting a task, with the `RawCause` in the error message showing `context deadline exceeded`?
 
-This is a known issue in DM 2.0.0 version and will be fixed in DM 2.0.1 version. It is likely to be triggered when a replication task has a lot of tables to process. If you use TiUP to deploy DM, you can upgrade DM to the nightly version to fix this issue. Or you can download the 2.0.0-hotfix version from [the release page of DM](https://github.com/pingcap/ticdc/releases) on GitHub and manually replace the executable files.
+This is a known issue in DM 2.0.0 version and will be fixed in DM 2.0.1 version. It is likely to be triggered when a replication task has a lot of tables to process. If you use TiUP to deploy DM, you can upgrade DM to the nightly version to fix this issue. Or you can download the 2.0.0-hotfix version from [the release page of DM](https://github.com/pingcap/tiflow/releases) on GitHub and manually replace the executable files.
 
 ## How to handle the error `duplicate entry` when DM is replicating data?
 

Diff for: en/open-api.md

@@ -18,7 +18,7 @@ openapi = true
 
 > **Note:**
 >
-> - DM provides the [specification document](https://github.com/pingcap/ticdc/blob/master/dm/openapi/spec/dm.yaml) that meets the OpenAPI 3.0.0 standard. This document contains all the request parameters and returned values. You can copy the document yaml and preview it in [Swagger Editor](https://editor.swagger.io/).
+> - DM provides the [specification document](https://github.com/pingcap/tiflow/blob/master/dm/openapi/spec/dm.yaml) that meets the OpenAPI 3.0.0 standard. This document contains all the request parameters and returned values. You can copy the document yaml and preview it in [Swagger Editor](https://editor.swagger.io/).
 >
 > - After you deploy the DM-master nodes, you can access `http://{master-addr}/api/v1/docs` to preview the documentation online.
 

Diff for: en/releases/5.3.0.md

@@ -15,7 +15,7 @@ In earlier versions (v1.0 and v2.0), DM uses version numbers that are independen
 ## Improvements
 
 - Reduce latency when Relay Log is enabled [#2225](https://github.com/pingcap/dm/pull/2225)
-- Compress/merge DML statements for incremental replication to reduce replication latency [#3162](https://github.com/pingcap/ticdc/pull/3162) [#3167](https://github.com/pingcap/ticdc/pull/3167)
+- Compress/merge DML statements for incremental replication to reduce replication latency [#3162](https://github.com/pingcap/tiflow/pull/3162) [#3167](https://github.com/pingcap/tiflow/pull/3167)
 - Support OpenAPI feature to better manage DM clusters (experimental feature) [#1928](https://github.com/pingcap/dm/issues/1982)
 - Optimize the user experience of dmctl and add subcommands [#1746](https://github.com/pingcap/dm/pull/1746)
 - Support for maintaining transaction atomicity when stopping or pausing replication tasks [#1928](https://github.com/pingcap/dm/pull/1928)
@@ -29,8 +29,8 @@ In earlier versions (v1.0 and v2.0), DM uses version numbers that are independen
 - Optimize logic for fetching status data from upstream sources to reduce pressure on upstream [#2076](https://github.com/pingcap/dm/pull/2076)
 - Report errors and prompt users when encountering unsupported binlog formats [#2099](https://github.com/pingcap/dm/pull/2099)
 - Support for batch manipulation of all sync tasks in a data source via dmctl [#2166](https://github.com/pingcap/dm/pull/2166)
-- Generate DML WHERE statements from downstream table schemas [#3168](https://github.com/pingcap/ticdc/pull/3168)
-- Support for automatic acquisition and configuration of upstream and downstream time zones [#3403](https://github.com/pingcap/ticdc/pull/3403)
+- Generate DML WHERE statements from downstream table schemas [#3168](https://github.com/pingcap/tiflow/pull/3168)
+- Support for automatic acquisition and configuration of upstream and downstream time zones [#3403](https://github.com/pingcap/tiflow/pull/3403)
 
 ## Bug fixes
 
@@ -42,8 +42,8 @@ In earlier versions (v1.0 and v2.0), DM uses version numbers that are independen
 - Fix the issue that dmctl returns unclear error messages [#2063](https://github.com/pingcap/dm/pull/2063)
 - Fix the issue of DM-worker scheduling failure when Relay Log is enabled [#2199](https://github.com/pingcap/dm/pull/2219)
 - Fix the issue that DM-worker fails to connect to the upstream database and to start when Relay Log is enabled [#2227](https://github.com/pingcap/dm/pull/2227)
-- Fix the issue of a meta file writing failure when Relay Log is enabled and upstream database switches [#3164](https://github.com/pingcap/ticdc/pull/3164)
+- Fix the issue of a meta file writing failure when Relay Log is enabled and upstream database switches [#3164](https://github.com/pingcap/tiflow/pull/3164)
 
 ## Known issues
 
-[GitHub issues](https://github.com/pingcap/ticdc/issues?q=is%3Aissue+is%3Aopen+label%3Atype%2Fbug+label%3Aarea%2Fdm)
+[GitHub issues](https://github.com/pingcap/tiflow/issues?q=is%3Aissue+is%3Aopen+label%3Atype%2Fbug+label%3Aarea%2Fdm)

Diff for: zh/_index.md

@@ -6,11 +6,11 @@ aliases: ['/docs-cn/tidb-data-migration/dev/']
 
 # TiDB Data Migration 用户文档
 
-[TiDB Data Migration](https://github.com/pingcap/ticdc/tree/master/dm) (DM) 是一款便捷的数据迁移工具，支持从与 MySQL 协议兼容的数据库（MySQL、MariaDB、Aurora MySQL）到 TiDB 的数据迁移。DM 工具旨在降低数据迁移的运维成本。
+[TiDB Data Migration](https://github.com/pingcap/tiflow/tree/master/dm) (DM) 是一款便捷的数据迁移工具，支持从与 MySQL 协议兼容的数据库（MySQL、MariaDB、Aurora MySQL）到 TiDB 的数据迁移。DM 工具旨在降低数据迁移的运维成本。
 
 > **注意：**
 >
-> - DM 的 GitHub 代码仓库已于 2021 年 10 月迁移至 [pingcap/ticdc](https://github.com/pingcap/ticdc/tree/master/dm)。如有任何关于 DM 的问题，请在 `pingcap/ticdc` 仓库提交，以获得后续反馈。
+> - DM 的 GitHub 代码仓库已于 2021 年 12 月迁移至 [pingcap/tiflow](https://github.com/pingcap/tiflow/tree/master/dm)。如有任何关于 DM 的问题，请在 `pingcap/tiflow` 仓库提交，以获得后续反馈。
 > - 在较早版本中（v1.0 和 v2.0），DM 采用独立于 TiDB 的版本号。从 DM v5.3 起，DM 采用与 TiDB 相同的版本号。DM v2.0 的下一个版本为 DM v5.3。DM v2.0 到 v5.3 无兼容性变更，升级过程与正常升级无差异，仅仅是版本号上的增加。
 
 <NavColumns>

Diff for: zh/deploy-a-dm-cluster-using-binary.md

@@ -21,7 +21,7 @@ aliases: ['/docs-cn/tidb-data-migration/dev/deploy-a-dm-cluster-using-binary/']
 
 > **注意：**
 >
-> 下载链接中的 `{version}` 为 DM 的版本号。例如，`v1.0.1` 版本的下载链接为 `https://download.pingcap.org/dm-v1.0.1-linux-amd64.tar.gz`。可以通过 [DM Release](https://github.com/pingcap/ticdc/releases) 查看当前已发布版本。
+> 下载链接中的 `{version}` 为 DM 的版本号。例如，`v1.0.1` 版本的下载链接为 `https://download.pingcap.org/dm-v1.0.1-linux-amd64.tar.gz`。可以通过 [DM Release](https://github.com/pingcap/tiflow/releases) 查看当前已发布版本。
 
 下载的文件中包括子目录 bin 和 conf。bin 目录下包含 dm-master、dm-worker 以及 dmctl 的二进制文件。conf 目录下有相关的示例配置文件。
 

Diff for: zh/faq.md

@@ -145,7 +145,7 @@ DM 在最后 `rename ghost_table to origin table` 的步骤会把内存的 DDL 
 
 ## DM v2.0.0 启动任务时出现 `fail to initial unit Sync of subtask`，报错信息的 `RawCause` 显示 `context deadline exceeded`
 
-该问题是 DM v2.0.0 的已知问题，在同步任务的表数目较多时触发，将在 v2.0.1 修复。使用 TiUP 部署的用户可以升级到开发版 nightly 解决该问题，或者访问 GitHub 上 [DM 仓库的 release 页面](https://github.com/pingcap/ticdc/releases)下载 v2.0.0-hotfix 版本手动替换可执行文件。
+该问题是 DM v2.0.0 的已知问题，在同步任务的表数目较多时触发，将在 v2.0.1 修复。使用 TiUP 部署的用户可以升级到开发版 nightly 解决该问题，或者访问 GitHub 上 [DM 仓库的 release 页面](https://github.com/pingcap/tiflow/releases)下载 v2.0.0-hotfix 版本手动替换可执行文件。
 
 ## DM 同步中报错 `duplicate entry`
 

Diff for: zh/open-api.md

@@ -18,7 +18,7 @@ openapi = true
 
 > **注意：**
 >
-> - DM 提供符合 OpenAPI 3.0.0 标准的 [Spec 文档](https://github.com/pingcap/ticdc/blob/master/dm/openapi/spec/dm.yaml)，其中包含了所有 API 的请求参数和返回体，你可自行复制到如 [Swagger Editor](https://editor.swagger.io/) 等工具中在线预览文档。
+> - DM 提供符合 OpenAPI 3.0.0 标准的 [Spec 文档](https://github.com/pingcap/tiflow/blob/master/dm/openapi/spec/dm.yaml)，其中包含了所有 API 的请求参数和返回体，你可自行复制到如 [Swagger Editor](https://editor.swagger.io/) 等工具中在线预览文档。
 >
 > - 部署 DM-master 后，你可访问 `http://{master-addr}/api/v1/docs` 在线预览文档。
 

Diff for: zh/releases/5.3.0.md

@@ -15,7 +15,7 @@ DM 版本：5.3.0
 ## 改进提升
 
 - 开启 Relay Log 同步时大幅度降低延迟 [#2225](https://github.com/pingcap/dm/pull/2225)
-- 增量同步时压缩/合并 DML 语句，大幅度降低同步延迟 [#3162](https://github.com/pingcap/ticdc/pull/3162) [#3167](https://github.com/pingcap/ticdc/pull/3167)
+- 增量同步时压缩/合并 DML 语句，大幅度降低同步延迟 [#3162](https://github.com/pingcap/tiflow/pull/3162) [#3167](https://github.com/pingcap/tiflow/pull/3167)
 - 支持通过 OpenAPI 运维管理 DM 集群（实验特性） [#1928](https://github.com/pingcap/dm/issues/1982)
 - 优化 dmctl 的使用体验并增加一些子命令 [#1746](https://github.com/pingcap/dm/pull/1746)
 - 支持停止或暂停同步任务时保持事务原子性 [#1928](https://github.com/pingcap/dm/pull/1928)
@@ -29,8 +29,8 @@ DM 版本：5.3.0
 - 优化获取数据源状态数据的逻辑，减少对上游的压力 [#2076](https://github.com/pingcap/dm/pull/2076)
 - 遇到不支持的 binlog 格式时，报错并提示用户 [#2099](https://github.com/pingcap/dm/pull/2099)
 - 支持通过 dmctl 批量操作数据源里的所有同步任务 [#2166](https://github.com/pingcap/dm/pull/2166)
-- 通过下游表结构来生成 DML WHERE 语句 [#3168](https://github.com/pingcap/ticdc/pull/3168)
-- 支持自动获取和配置上下游的时区 [#3403](https://github.com/pingcap/ticdc/pull/3403)
+- 通过下游表结构来生成 DML WHERE 语句 [#3168](https://github.com/pingcap/tiflow/pull/3168)
+- 支持自动获取和配置上下游的时区 [#3403](https://github.com/pingcap/tiflow/pull/3403)
 
 ## Bug 修复
 
@@ -42,8 +42,8 @@ DM 版本：5.3.0
 - 修复 dmctl 返回错误信息不明确的问题 [#2063](https://github.com/pingcap/dm/pull/2063)
 - 修复开启 Relay Log 时 DM-worker 调度失败的问题 [#2199](https://github.com/pingcap/dm/pull/2219)
 - 修复开启 Relay Log 时 DM-worker 不能连接上游而启动失败的问题 [#2227](https://github.com/pingcap/dm/pull/2227)
-- 修复开启 Relay Log 且上游发生切换时 meta 文件写入失败的问题 [#3164](https://github.com/pingcap/ticdc/pull/3164)
+- 修复开启 Relay Log 且上游发生切换时 meta 文件写入失败的问题 [#3164](https://github.com/pingcap/tiflow/pull/3164)
 
 ## 已知问题
 
-[GitHub issues](https://github.com/pingcap/ticdc/issues?q=is%3Aissue+is%3Aopen+label%3Atype%2Fbug+label%3Aarea%2Fdm)
+[GitHub issues](https://github.com/pingcap/tiflow/issues?q=is%3Aissue+is%3Aopen+label%3Atype%2Fbug+label%3Aarea%2Fdm)