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
*: remove tikv-importer #5036
*: remove tikv-importer #5036
Conversation
54ca51d
to
5f439af
Compare
The KV importer service has been extracted into the tikv/importer repository. Only the SST importer service needs to remain here. All code related to the KV importer has been removed here. Signed-off-by: kennytm <kennytm@gmail.com>
5f439af
to
ef559e4
Compare
/run-integration-tests |
If we can support a plugin which can let the user register their own gRPC server, maybe we can make code cleaner, right? @kennytm |
@siddontang Certainly. But that may make using Importer harder, since that ImportSSTService plugin will need to be installed on every TiKV node. |
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
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
Could you move |
@overvenus OK, will move in another PR. |
/run-integration-tests |
I guess it is spurious. /test |
/run-integration-common-test |
The KV importer service has been extracted into the tikv/importer repository. Only the SST importer service needs to remain here. All code related to the KV importer has been removed here. Signed-off-by: kennytm <kennytm@gmail.com>
Signed-off-by: kennytm kennytm@gmail.com
What have you changed? (mandatory)
The KV importer service has been extracted into the tikv/importer repository. Only the SST importer service needs to remain here. All code related to the KV importer has been removed here.
What are the type of the changes? (mandatory)
How has this PR been tested? (mandatory)
cargo check
Does this PR affect documentation (docs) or release note? (mandatory)
Does this PR affect tidb-ansible update? (mandatory)
No, the binary has already been switched to be packaged from tikv/importer.
Refer to a related PR or issue link (optional)
Benchmark result if necessary (optional)
Add a few positive/negative examples (optional)