Re:RethinkDB 1.10: multi-indexing
by continuations on Monday September 30, 2013 @09:45PM
(#6473553)
> but we do a number of systems tricks to make this really efficient.
Can you talk about these tricks? I'd love to learn more about it.
We store a secondary index for a shard on the same node where the master for the shard resides. So if you're storing users whose last names are between A-M on node A, all secondary indexes for users with last names between A and M will also be on node A. That means that for any secondary index query we have to contact all nodes that have shards for a table, but we do a number of systems tricks to make this really efficient.