[SERVER-4325] BasicCursor may be reported by explain when a query cannot match any documents Created: 18/Nov/11 Updated: 10/Dec/14 Resolved: 01/Nov/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Aaron Staple | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | query_triage | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
In some cases the query optimizer may determine that a query cannot match any documents. In these cases it will generate a trivial BasicCursor that will scan zero documents. Explain will report using this BasicCursor, which can be a usability issue as seen in |