[SERVER-5759] indexOnly in explain() is not reported correctly Created: 03/May/12 Updated: 03/Mar/15 Resolved: 11/Feb/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics, Index Maintenance, Querying |
| Affects Version/s: | None |
| Fix Version/s: | 2.8.0-rc0 |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | siddharth.singh@10gen.com | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 2 |
| Labels: | coveredIndex, query_triage | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||||||
| Description |
|
Expected indexOnly:false but it is reported as true.
|
| Comments |
| Comment by Asya Kamsky [ 11/Feb/15 ] | |||||||||||||||||||||||||||
|
Resolved via explain plan changes for 3.0.0 | |||||||||||||||||||||||||||
| Comment by A. Jesse Jiryu Davis [ 09/Jul/13 ] | |||||||||||||||||||||||||||
|
For example:
| |||||||||||||||||||||||||||
| Comment by auto [ 14/Feb/13 ] | |||||||||||||||||||||||||||
|
Author: {u'date': u'2013-02-15T06:26:56Z', u'name': u'aaron', u'email': u'aaron@10gen.com'}Message: | |||||||||||||||||||||||||||
| Comment by Aaron Staple [ 12/Sep/12 ] | |||||||||||||||||||||||||||
|
List (partial) of criteria that go into determining whether a query is index only (these should be used for reporting):
Currently the reported indexOnly field is just based on Projection::KeyOnly. |