pingcap / pingcap/tidb-operator
The backup files are not compressed while using dumpling to GCS
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 540
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 18
Description
Feature Request
Is your feature request related to a problem? Please describe:
While using dumpling to back up the data of the TiDB cluster in Kubernetes to GCS. The backup data will be shrunk into a tgz file to upload. The TiDB cloud can not use this file to import data directly.
Describe the feature you'd like:
I can choose whether the backup data be compressed to upload to GCS while using the dumpling to backup the TiDB cluster in Kubernetes.
Describe alternatives you've considered:
Teachability, Documentation, Adoption, Migration Strategy:
The user who wants to back up the data of TiDB Cluster in Kubernetes and with data migration to TiDB Cloud.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing dumpling's backup path for Kubernetes clusters and its upload handling for GCS. Determine where compression is selected or applied, then define the configuration behavior needed for compressed and uncompressed uploads. Done means a user can choose the format and TiDB Cloud can import the uncompressed backup data directly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, google-cloud, kubernetes
- Domain
- cloud, data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100