key-value sharding questions / examples about actordb HOT 2 CLOSED

1. actor name is a key and yes they are indexed. This type of query is fine:

ACTOR type1(* where id like 'some_prefix%');

2. kv actors are always across multiple shards. ~12 per cluster.

3. When you add new clusters, shards will get split in half. The first half remains on the old servers, the top half goes to new nodes. It is automatic. Basically what happens is a copy of the complete shard to the new node, then the origin shard runs delete * from actors where hash >= SPLIT_POINT and the new shard runs delete * from actors where hash < SPLIT_POINT.

4. This pretty much covers the main points of the functionality. http://www.actordb.com/docs-kvstore.html#about_kv_store

5. Sub table needs to be linked to the main key so that sharding works. delete * from actors where hash >= SPLIT_POINT must delete all data for keys that are no longer required. And when you query for data to subtable it must be in the same shard as the main actors table.

from actordb.

Thanks @SergejJurecko, very helpful.

from actordb.