-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.0.3
-
Component/s: Querying
-
None
-
ALL
-
It seems like the query planner ignores one of the range ends, and scans the index from the beginning. Obviously the query is unreasonably slow on large collections - up to 1 hour on the collection with ~20M records. Am i missing something or is it a bug?
- duplicates
-
SERVER-15086 Allow for efficient range queries over non-array fields in multikey indices
- Closed