Jay
Although I updated the RFC to write latest CF first, and then move keys between CFs, I suggest to always double write in POC as it has less compatibility issues.
Key spaces sound like a solution to the problem tikv/tikv#3922. And it may also be useful if we want to implement multi-tenancy in cloud.
The RFC is quite simple yet. For example, how is the new node designed? How it triggers GC? How does GC work in details? What's the triggering frequency?
So should I review key space first?
You mean reset data to certain mvcc snapshot, right?
Thanks for recommendation! It's a fantastic library! In yatp, tasks don't have fixed priority, which doesn't seem to fit in the model though.
It means you are probably using an outdated version. The API exists on master branch and is not released yet.
It introduces clang dependency, which can be a pain to fix. You can learn how to avoid it from tikv/grpc-rs.
There are also a few things to do: - [ ] Update README and Cargo.toml to use the latest name - [ ] Cleanup Cargo.toml to remove unnecessary dependencies or...
tirocks can use its own version and release schedule just like grpcio or raft-rs. Besides, I don't think tirocks can reach 1.0 yet. It needs to fill a lot of...