[SERVER-9495] sort/limit optimization with {$in} expression isn't used if null is one of the values for $in. Created: 28/Apr/13 Updated: 06/Dec/22 Resolved: 06/Mar/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance |
| Affects Version/s: | 2.4.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Asya Kamsky | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | indexing, query | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query
|
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Participants: |
| Description |
|
This looks like a partial regression of My test:
correctly limits documents (nscanned and nscannedObject to 10).
same thing. 2.4.x query:
correctly limits to 10 docs.
scans all matching a documents without applying limit. |
| Comments |
| Comment by Asya Kamsky [ 06/Mar/16 ] |
|
No longer an issue in any supported version. |
| Comment by Asya Kamsky [ 28/Apr/13 ] |
|
Correction, I think technically it's a regression of |