3 ms·

I'll ask the same question that I had about RethinkDB last week [1]: how does TokuMX handle secondary indexes on a sharded database? Since it doesn't support c

I'll ask the same question that I had about RethinkDB last week [1]: how does TokuMX handle secondary indexes on a sharded database? Since it doesn't support cross-shard atomic operations, I'm assuming it takes the same approach as RethinkDB, i.e. co-locating data with its index entries, which means index lookups require querying every shard in the cluster. But I don't see this explicitly stated in the user's guide, so it would be nice to get some confirmation. [1] https://news.ycombinator.com/item?id=5876168 https://news.ycombinator.com/item?id=5876168

leif 13y ago
The sharing architecture is the same as mongodb: data is partitioned based according to a shard key and the secondary indexes are built separately on each shard. So queries that use indexes other than the shard key must be broadcast. For 1.0 we wanted to match mongodb feature-wise as broadly as possible. However, fractal trees can handle multiple clustered indexes very well, and this extends to a few ideas I have for adding things to do sharding in what I think will be a much better way. It's a bit up in the air right now but I can tell you we plan to make some significant innovations here, and if you have experience you can share, you should email us and we can talk it over and maybe change what we end up doing.
deleted 13y ago
[deleted]
deleted 13y ago
[deleted]