cloud: add TiDB Serverless Export #16969
Conversation
ti-chi-bot
bot
added
missing-translation-status
shiyuhang0
force-pushed
the
support_export
branch
from
c484f1c to
f59d72f
Compare
qiancai
added
translation/no-need
ti-chi-bot
bot
removed
the
missing-translation-status
shiyuhang0
force-pushed
the
support_export
branch
from
da8fc5e to
e6ad63d
Compare
Co-authored-by: Lilian Lee <[email protected]>
Co-authored-by: Lilian Lee <[email protected]>
|
|
||
| While you can also export data using tools such as [mysqldump](https://dev.mysql.com/doc/refman/8.0/en/mysqldump.html) and TiDB [Dumpling](https://docs.pingcap.com/tidb/dev/dumpling-overview), TiDB Serverless Export offers a more convenient and efficient way to export data from a TiDB Serverless cluster. It brings the following benefits: | ||
|
|
||
| - Convenience: the export service provides a simple and easy-to-use way to export data from a TiDB Serverless cluster, eliminating the need for additional tools or resources. |
There was a problem hiding this comment.
One more advantage is you don't have to take care of memory allcoation. For mysqldump and dumpling, it's easy to exceed memory limitation, especially for free tier the limitation is only 256MiB.
|
@zhangyangyu: adding LGTM is restricted to approvers and reviewers in OWNERS files. In response to this: Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
ti-chi-bot
bot
added
lgtm
and removed
needs-1-more-lgtm
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: qiancai The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
First-time contributors' checklist
What is changed, added or deleted? (Required)
see #16776 for review details
Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions.
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?