-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
GSoC: High-performance import tool for TiKV #9778
Comments
|
/assign @Abingcbc |
|
@andylokandy: GitHub didn't allow me to assign the following users: Abingcbc. Note that only tikv members, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time. 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. |
|
/assign @Abingcbc |
|
I want to export from one tikv to another tikv , do you have a good solution? @andylokandy |
@mikechengwei in this case you may want to use BR. |
Description
TiKV has two import tools, one is the
importerwhich has been passively maintained since 4.0 and lack some new optimizations, the other one istidb-lightningwhich has been merged intoBRrecently, but thetidb-lightningonly supports importing SQL-like data into TiKV.This issue aims to split
tidb-lightninginto two parts: (1) translating SQL data into KV pair, and (2) importing KV pairs into TiKV. By splitting into these two steps, we can support importing KV-like data into TiKV, e.g. migrating from Cassandra to TiKV. The size of data being imported is about 50TB.Related issue: pingcap/br#764
GSoC Program information
Milestones and action items
Milestone 1: Implement the import tool with simple
batch_put.Pebble.batch_putthe sorted data.batch_putMilestone 2: Implement the import tool with Ingest SST.
The text was updated successfully, but these errors were encountered: