4 ms·
See https://tikv.org/deep-dive/key-value-engine/introduction/ https://tikv.org/deep-dive/key-value-engine/introduction/. You can specify the storage engine, alt
by ergl 6y ago
See https://tikv.org/deep-dive/key-value-engine/introduction/ https://tikv.org/deep-dive/key-value-engine/introduction/. You can specify the storage engine, although all the available engines in that page order the keys: rocksdb allows prefix search, and both B and LSM trees naturally order keys.
- rapsey 6y agoStorage engine on a node using ordered keys is not the same thing as a distributed KV store maintaining an ordered index.
- ergl 6y agoI'm not entirely sure about what you mean, and I'm not terribly familiar with TiKV. In general, a single node partition will use ordered storage. At a higher level (partitions/shards), you use either key ranges or hashing to route keys to partitions: https://tikv.org/deep-dive/scalability/data-sharding/ https://tikv.org/deep-dive/scalability/data-sharding/ It seems TiKV uses range partitioning, so that's giving you the order across nodes.