client-rust
client-rust copied to clipboard
tikv
Rust Client for TiKV.
We should provide benchmark results for each release. It's also meaningful to guide performance optimization.
Currently `pessimistic_lock` will always issue a request. If heartbeat is enabled, we don't have to lock the same key for multiple times. For `get_for_update`-like operations, we can have a separate...
A request involving multiple regions can be parallelized. We may also need to consider the maximum concurrency. If there are too many concurrent requests, TiKV is likely to report "server...
Current situation: - We only have simple integration tests under `tests/integration_tests.rs`. - The error handling paths are not well tested. We need to: - Test with various workload - Test...
## For initial release - [x] Introduction (readme, include in rustdoc, check crate root docs) - Public API of main crate - [x] RawClient - [ ] ColumnFamily - [x]...
Currently, we automatically resolve locks and retry (without bumping the start ts which would be unsound). This is ok as a default, but it would be nice to also allow...
Debugging and handling errors is sub-optimal. Our errors are pretty good for the general case, and for just printing an error to a log or whatever, but if you're actually...
I'm not sure if this is a feature or a bug.
## Description Normal resolve lock scans the whole region for locks. With resolve lock lite, we resolve only the specified locks. This can reduce TiKV's load when there are a...
