From 13fa485e2dd76d0481853315cfe899a48a18dd38 Mon Sep 17 00:00:00 2001 From: Ran Date: Fri, 14 Jan 2022 22:55:43 +0800 Subject: [PATCH] fix chinese periods (#7408) --- dm/maintain-dm-using-tiup.md | 2 +- dm/quick-create-migration-task.md | 4 ++-- dm/quick-start-create-source.md | 6 +++--- migrate-small-mysql-shards-to-tidb.md | 2 +- 4 files changed, 7 insertions(+), 7 deletions(-) diff --git a/dm/maintain-dm-using-tiup.md b/dm/maintain-dm-using-tiup.md index 2f752f5914565..0a42f0658061f 100644 --- a/dm/maintain-dm-using-tiup.md +++ b/dm/maintain-dm-using-tiup.md @@ -179,7 +179,7 @@ For example, to scale out a DM-worker node in the `prod-cluster` cluster, take t > **Note:** > -> Since v2.0.5, dmctl support [Export and Import Data Sources and Task Configuration of Clusters](/dm/dm-export-import-config.md)。 +> Since v2.0.5, dmctl support [Export and Import Data Sources and Task Configuration of Clusters](/dm/dm-export-import-config.md). > > Before upgrading, you can use `config export` to export the configuration files of clusters. After upgrading, if you need to downgrade to an earlier version, you can first redeploy the earlier cluster and then use `config import` to import the previous configuration files. > diff --git a/dm/quick-create-migration-task.md b/dm/quick-create-migration-task.md index 9b6e749319f2c..58337a62fa2f2 100644 --- a/dm/quick-create-migration-task.md +++ b/dm/quick-create-migration-task.md @@ -9,8 +9,8 @@ summary: Learn how to configure a data migration task in different scenarios. > > Before creating a data migration task, you need to perform the following operations: > -> 1. [Deploy a DM Cluster Using TiUP](/dm/deploy-a-dm-cluster-using-tiup.md)。 -> 2. [Create a Data Source](/dm/quick-start-create-source.md)。 +> 1. [Deploy a DM Cluster Using TiUP](/dm/deploy-a-dm-cluster-using-tiup.md). +> 2. [Create a Data Source](/dm/quick-start-create-source.md). This document introduces how to configure a data migration task in different scenarios. You can choose suitable documents to create your data migration task according to the specific scenario. diff --git a/dm/quick-start-create-source.md b/dm/quick-start-create-source.md index 0317048154176..6fb5db8236631 100644 --- a/dm/quick-start-create-source.md +++ b/dm/quick-start-create-source.md @@ -7,7 +7,7 @@ summary: Learn how to create a data source for Data Migration (DM). > **Note:** > -> Before creating a data source, you need to [Deploy a DM Cluster Using TiUP](/dm/deploy-a-dm-cluster-using-tiup.md)。 +> Before creating a data source, you need to [Deploy a DM Cluster Using TiUP](/dm/deploy-a-dm-cluster-using-tiup.md). The document describes how to create a data source for the data migration task of TiDB Data Migration (DM). @@ -35,7 +35,7 @@ A data source contains the information for accessing the upstream migration task ```yaml source-id: "mysql-01" # The ID of the data source, you can refer this source-id in the task configuration and dmctl command to associate the corresponding data source. - + from: host: "127.0.0.1" port: 3306 @@ -89,7 +89,7 @@ After creating a data source, you can use the following command to query the dat ```bash tiup dmctl --master-addr get-config source mysql-01 ``` - + ``` { "result": true, diff --git a/migrate-small-mysql-shards-to-tidb.md b/migrate-small-mysql-shards-to-tidb.md index 141b54706ca20..65ffec53032fc 100644 --- a/migrate-small-mysql-shards-to-tidb.md +++ b/migrate-small-mysql-shards-to-tidb.md @@ -231,7 +231,7 @@ You can view the history of a migration task and internal operational metrics th ## See also -- [Migrate and Merge MySQL Shards of Large Datasets to TiDB](/migrate-large-mysql-shards-to-tidb.md)。 +- [Migrate and Merge MySQL Shards of Large Datasets to TiDB](/migrate-large-mysql-shards-to-tidb.md). - [Merge and Migrate Data from Sharded Tables](https://docs.pingcap.com/tidb-data-migration/stable/feature-shard-merge) - [Best Practices of Data Migration in the Shard Merge Scenario](https://docs.pingcap.com/tidb-data-migration/stable/shard-merge-best-practices) - [Handle Errors](https://docs.pingcap.com/tidb-data-migration/stable/error-handling)