-
Notifications
You must be signed in to change notification settings - Fork 687
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
tools: add a guide for choosing TiDB Ecosystem Tools #1860
tools: add a guide for choosing TiDB Ecosystem Tools #1860
Conversation
@WangXiangUSTC Please also refer to related changes in #2244 when you review the English version. Pay attention to the new file name. Thanks! |
After this PR is given two LGTMs, I will commit to this PR according to the changes related to this document made in #2244. |
reference/tools/user-guide.md
Outdated
- Applicable version of TiDB: All. | ||
- Kubernetes: Not supported. | ||
|
||
#### Incremental import tool TiDB Data Migration |
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.
DM support incremental and full data's export and import.
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.
Thanks a lot.
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.
rest LGTM
reference/tools/user-guide.md
Outdated
|
||
### Data import tools | ||
|
||
#### Full import tool loader (Stop maintenance, not recommended) |
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.
If Loader is deprecated, it is better to not lead with it, but instead lead with lightning and then mention that loader still exists but is deprecated.
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.
We could consider even having a separate section for deprecated tools.
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.
Thanks a lot.
Co-Authored-By: Greg Weber <greg@gregweber.info>
Co-Authored-By: Greg Weber <greg@gregweber.info>
Co-Authored-By: Greg Weber <greg@gregweber.info>
Co-Authored-By: Greg Weber <greg@gregweber.info>
Co-Authored-By: Greg Weber <greg@gregweber.info>
Co-Authored-By: Greg Weber <greg@gregweber.info>
Co-Authored-By: TomShawn <41534398+TomShawn@users.noreply.github.com>
Co-Authored-By: TomShawn <41534398+TomShawn@users.noreply.github.com>
@lilin90 The lint failure is fixed. |
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
@yikeke @toutdesuite #2244 is aligned in this PR, PTAL, thanks! |
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.
Rest LGTM
Co-Authored-By: Keke Yi <40977455+yikeke@users.noreply.github.com>
/run-all-tests |
Signed-off-by: sre-bot <sre-bot@pingcap.com>
cherry pick to release-2.1 in PR #2035 |
Signed-off-by: sre-bot <sre-bot@pingcap.com>
cherry pick to release-3.0 in PR #2036 |
Signed-off-by: sre-bot <sre-bot@pingcap.com>
cherry pick to release-3.1 in PR #2037 |
* cherry pick #1860 to release-3.0 Signed-off-by: sre-bot <sre-bot@pingcap.com> * resolve conflicts * update version numbers and replace links Co-authored-by: toutdesuite <guizhiluo2014@163.com> Co-authored-by: TomShawn <1135243111@qq.com> Co-authored-by: TomShawn <41534398+TomShawn@users.noreply.github.com>
What is changed, added or deleted?
Now we have too many tools, users may don't know how to choose. So we need add a guide, tells users every tool's usage scenario.
What is the related PR or file link(s)?
Important Notice:
If your changes apply to multiple TiDB documentation versions, to trigger the bot to cherry-pick this PR to other release branches, make sure you add labels such as: