You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For DynamoDb and ScyllaDb, we could access the root keys easily since they are partition keys.
The RocksDb does not have a notion of partition key.
Instead, we simply concatenate the keys like root_key + key.
This design was chosen because having one RocksDB instance per root key would lead to an overflow in the number of opened files.
One idea would be to add some entry indicating the creation of a new root key when doing a clone_with_root_key. This would make the clone_with_root_key async but that is fine.
The support in storage service would also be somewhat difficult. But a priori possible.
The text was updated successfully, but these errors were encountered:
We are currently using the
root_key
in theAdminKeyValueStore
. This is a formalization of the notion of partition keys in databases.What is missing is the ability to get the list of root keys. That is we would like to have
There are two use cases for that:
There are obstacles to that:
RocksDb
does not have a notion of partition key.root_key + key
.clone_with_root_key
. This would make theclone_with_root_key
async but that is fine.The text was updated successfully, but these errors were encountered: