If a special index type is hinted but is not considered "suitable", the code in QueryPlan::newCursor instantiates its own btree rather than just handing off to the custom "newCursor" code for that index. This is probably incorrect behavior (I believe the btree bounds that it comes up with can be incorrect for special indexes). One way to to fix this is to initialize "_type" earlier, and make sure the custom newCursor methods handle being used for unsuitable queries.
- is depended on by
-
SERVER-2001 option to hash shard key
-
- Closed
-
- related to
-
-
- Closed
-
-
-
- Closed
-