-
Notifications
You must be signed in to change notification settings - Fork 688
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
export #16776
export #16776
Conversation
Co-authored-by: Daniël van Eeden <[email protected]>
Co-authored-by: Daniël van Eeden <[email protected]>
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/verify |
When you export to local, there are some limitations: | ||
|
||
1. You can only export one table at a time. | ||
2. The exported data will be expired after two days, please download the data in time. |
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.
Does it mean the exported data will be removed from the stashing area when it has been downloaded for two days?
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.
it will be removed from the stashing area after three days, but it will not be allowed to download after two days.
tidb-cloud/serverless-export.md
Outdated
|
||
> **Note:** | ||
> | ||
> We recommend you export to S3 or other supported storage services if you want to export a large amount of data. |
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.
"other supported storage services" looks unclear. Currently, besides S3, what storage services are supported for this feature?
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.
only s3 is supported now, we will support GCS (Google cloud storage) and Azure Blob Storage next Q
tidb-cloud/serverless-export.md
Outdated
|
||
<div label="Export On Console"> | ||
|
||
Not supported yet. |
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.
When is it planned? If it will not happen in the upcoming one or two months, can we remove this tab and tell users that currently they can only use this feature with the CLI?
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.
It should be supported in the next quarter (before july)
tidb-cloud/serverless-export.md
Outdated
|
||
## Export to S3 | ||
|
||
You can export data directly to your own S3 bucket with the credentials. |
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.
Are there any permissions required for S3? Do we need to indicate the permissions here and also provide the S3 doc link about how to configure the permissions?
Co-authored-by: Grace Cai <[email protected]>
@shiyuhang0: The following test failed, say
Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
First-time contributors' checklist
What is changed, added or deleted? (Required)
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?