Get desktop application:
View/edit binary Protocol Buffers messages
ImportKV provides a service to import key-value pairs to TiKV. In order to import key-value pairs to TiKV, the user should: 1. Open an engine identified by an UUID. 2. Open write streams to write key-value batches to the opened engine. Different streams/clients can write to the same engine concurrently. 3. Close the engine after all write batches have been finished. An engine can only be closed when all write streams are closed. An engine can only be closed once, and it can not be opened again once it is closed. 4. Import the data in the engine to the target cluster. Note that the import process is not atomic, it requires the data to be idempotent on retry. An engine can only be imported after it is closed. An engine can be imported multiple times, but can not be imported concurrently. 5. Clean up the engine after it has been imported. Delete all data in the engine. An engine can not be cleaned up when it is writing or importing.
Switch the target cluster to normal/import mode.
(message has no fields)
Open an engine.
(message has no fields)
Open a write stream to the engine.
Write to engine, single message version
Close the engine.
Import the engine to the target cluster.
(message has no fields)
Clean up the engine.
(message has no fields)
Compact the target cluster for better performance.
(message has no fields)
Get current version and commit hash
(message has no fields)
Get importer metrics
(message has no fields)
Used in:
,This can happen if the client hasn't opened the engine, or the server restarts while the client is writing or closing. An unclosed engine will be removed on server restart, so the client should not continue but restart the previous job in that case.
Used in:
Used in:
Used in:
Used in:
Used in:
Used as response type in: ImportKV.WriteEngine, ImportKV.WriteEngineV3
Used in: