[shardingsphere] branch master updated: Update migration limitations doc (#24668)

[du...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

duanzhengqiang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/shardingsphere.git


The following commit(s) were added to refs/heads/master by this push:
     new 222801acf6b Update migration limitations doc (#24668)
222801acf6b is described below

commit 222801acf6b7e5bbc9aca6960599596021db80c8
Author: Hongsheng Zhong <zh...@apache.org>
AuthorDate: Sat Mar 18 22:09:21 2023 +0800

    Update migration limitations doc (#24668)
---
 docs/document/content/features/migration/limitations.cn.md | 12 +++++++-----
 docs/document/content/features/migration/limitations.en.md | 10 ++++++----
 2 files changed, 13 insertions(+), 9 deletions(-)

diff --git a/docs/document/content/features/migration/limitations.cn.md b/docs/document/content/features/migration/limitations.cn.md
index ae3a7739b73..ea8f06d3875 100644
--- a/docs/document/content/features/migration/limitations.cn.md
+++ b/docs/document/content/features/migration/limitations.cn.md
@@ -6,11 +6,13 @@ weight = 2
 ## 支持项
 
 * 将外围数据迁移至 Apache ShardingSphere 所管理的数据库；
-* 迁移含整型唯一键或字符串唯一键的表；
-* 迁移含整型主键或字符串主键的表。
+* 目标端 proxy 不配置规则或配置任意规则；
+* 迁移单字段主键或唯一键的表，首字段类型：整型、字符型、部分二进制类型（比如 MySQL VARBINARY）；
+* 迁移复合主键或复合唯一键的表。
 
 ## 不支持项
 
-* 迁移无主键且无唯一键的表；
-* 迁移复合主键或复合唯一键的表；
-* 不支持在当前存储节点之上做迁移，需要准备一个全新的数据库集群作为迁移目标库。
+* 不支持在当前存储节点之上做迁移，需要准备一个全新的数据库集群作为迁移目标库；
+* 不支持目标端 proxy 使用 HINT 分片策略；
+* 不支持目标端表结构和源端不一致；
+* 不支持迁移过程中源端表结构变更。
diff --git a/docs/document/content/features/migration/limitations.en.md b/docs/document/content/features/migration/limitations.en.md
index 6f46480a79f..79ea7773b8a 100644
--- a/docs/document/content/features/migration/limitations.en.md
+++ b/docs/document/content/features/migration/limitations.en.md
@@ -6,11 +6,13 @@ weight = 2
 ## Procedures Supported
 
 * Migration of peripheral data to databases managed by Apache ShardingSphere.
-* Migration of integer or string unique key tables.
-* Migration of integer or string primary key tables.
+* Target proxy without rule or configure any rule.
+* Migration of single column primary key or unique key table, the first column type could be: integer data type, string data type and part of binary data type (e.g. MySQL VARBINARY).
+* Migration of multiple column primary keys or unique keys table.
 
 ## Procedures not supported
 
-* Migration without primary key and unique key tables.
-* Migration of composite primary key or composite unique key tables.
 * Migration on top of the current storage node is not supported, so a brand new database cluster needs to be prepared as the migration target cluster.
+* Target proxy table rule contains HINT strategy.
+* Use different target table schema from source table schema.
+* Source table DDL changes during migration.