[SERVER-12529] incorrect explain output for covered $or with new query framework Created: 29/Jan/14 Updated: 11/Jul/16 Resolved: 04/Mar/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | 2.5.5 |
| Fix Version/s: | 2.6.0-rc1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Samantha Ritter (Inactive) | Assignee: | Samantha Ritter (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | query | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
mac os x |
||
| Attachments: |
|
||||||||||||
| Issue Links: |
|
||||||||||||
| Operating System: | OS X | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
On a covered $or query, we expect no objects to be scanned. For each clause, the "nscannedObjects" field is 0, but for the overall query, the "nscannedObjects" field is equal to "nscanned" and > 0. |
| Comments |
| Comment by Githook User [ 04/Mar/14 ] |
|
Author: {u'username': u'samantharitter', u'name': u'Samantha Ritter', u'email': u'samantha.ritter@10gen.com'}Message: Signed-off-by: Matt Kangas <matt.kangas@mongodb.com> |