-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
*: refine data migration document #2244
Conversation
LGTM |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
dev/TOC.md
Outdated
@@ -51,11 +51,9 @@ | |||
- [概述](/dev/how-to/monitor/overview.md) | |||
- [监控 TiDB 集群](/dev/how-to/monitor/monitor-a-cluster.md) | |||
+ 迁移 | |||
- [概述](/dev/how-to/migrate/overview.md) | |||
- [工具使用指南](/dev/reference/tools/use-guide.md) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1、这个链接应该指向迁移方案那一部分,而不是所有工具的指南
2、原来的[概述]被删掉了,里面有一些好的地方。比如,新加的这个指南里,“什么场景使用什么样的迁移方式”感觉可以再清晰一些(简写了建议的思路):
a、MySQL 1T 以上:mydumper+lightning 全量,dm 做增量(这个文档貌似没有)
b、MySQL 1T 以下:dm 全量+增量(已经有了)
c、非 MySQL,如 CSV
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
这个指南里面也涉及 “什么场景使用什么样的迁移方式”,而且更加合理和全面。其实 1T 这个算是拍脑袋的数据。 此外合并两个文档的原因是,不想维护两份,另外这个指南其实都是迁移相关,可能名字不够直接
title: 从 Amazon Aurora MySQL 迁移数据 | ||
summary: 使用 DM 从 Amazon Aurora MySQL 迁移数据。 | ||
title: 从 MySQL/Amazon Aurora MySQL 迁移数据 | ||
summary: 使用 DM 从 MySQL/Amazon Aurora MySQL 迁移数据。 | ||
category: how-to | ||
--- | ||
|
||
# 从 Amazon Aurora MySQL 迁移数据 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
# 从 Amazon Aurora MySQL 迁移数据 | |
# 从 MySQL/Amazon Aurora MySQL 迁移数据 |
还需在各版本
|
@@ -1,6 +1,7 @@ | |||
--- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- 这个文件取代了原迁移概述,内容性质一样,也很重要,属于直接使用类,而非辅助参考类,不建议放在 reference 下,建议采用原来的目录即可:
dev/how-to/migrate/overview.md
。因为这篇文档是总括性质的,个人认为可以用overview.md
。 数据迁移解决方案
提到工具演进路线
前面?演进路线更像一个参考类内容,个人认为解决方案内容的优先级高于演讲路线。
@kissmydb 怎么看?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- 原来的概述不是“直接使用类”的,是介绍可以用什么工具来进行全量备份和恢复,是 “指引类” 的,
use-guide.md
也是指引类的。 - 这个 link 直接跳转到
tidb-集群数据的全量备份及恢复
另外用户反馈 use-guide.md
这个 page 可以让他们获得他们想要的所有信息,所以我们集中只维护一个 “指引类” 的页面
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@GregoryIan
- 这里概述的功能是指引用户如何根据自己的场景选择工具,是直接使用前必要的一步;而参考类文档通常带有辅助性质。所以,放在前面的目录里更能凸显重要性。
- 在 how-to 的迁移章节只放一个链接的话,PDF 用户无法在前面得到想要的信息。建议将该文档放在 how-to 里,下面的 reference 工具下放链接。
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
我们不是都是靠 TOC 来索引的吗? 所以具体内容放在哪里其实没有关系。为什么放在 reference/tools 下面是因为,有人反馈过,他们习惯性去 reference/tools 下面找 tools 的所有文档,反而不会去 how-to
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
其实我不太明白,你表达什么 @lilin90
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
What is changed, added or deleted?
refine document releated data migration
syncer
/loader
,migrate/from-mysql.md
andincrementally-from-mysql.md
迁移概述
by工具使用指南
工具使用指南 3.0
What is the related PR or file link(s)?
Which TiDB version(s) does your changes apply to?
Note: If your changes apply to multiple TiDB versions, make sure you update the documents in the corresponding version folders such as "dev", "v3.0", "v2.1" and "v3.1" in this PR.