4 ms·

So, no secondary indexes right? Will doing a query like "age > 25" perform something equivalent to a full table scan?

• coffeemug 14y ago
  Yes, there are no secondary indexes right now (they're coming, but it will take a little time). Currently "age > 25" will do a scan, but if the db is sharded it will touch only the relevant shards and the query will be completely parallelized. We also do internal sharding for multicore performance, and the query will be parallelized across cores as well. All of that is only good for relatively small amounts of data though, so we'll be adding secondary indexes soon.
  • spicyj 14y ago
    How does it know which shards are relevant? I thought that data was sharded by primary key.
    • coffeemug 14y ago
      Err, sorry, my mistake -- pulled an all nighter to push the product out :) You're right, the system will have to scan every shard. (the statement above regarding parallelization is correct, though)
      • spicyj 14y ago
        No problem, huge congrats on shipping!
• jdoliner 14y ago
  Correct currently no secondary indices. Ranges on fields other than the primary key will require a full table scan. -Joe Doliner, engineer at RethinkDB