[SERVER-3127] ability to explain a distinct query Created: 20/May/11 Updated: 12/Jul/16 Resolved: 21/May/11 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance |
| Affects Version/s: | 1.8.0 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Alvin Richards (Inactive) | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Improvement: > db.blogs.distinct("author") > db.blogs.distinct("author").explain() |
| Comments |
| Comment by Craig Younkins [ 14/Oct/11 ] |
|
Note that Eliot's comment refers to stats when running distinct in the form of db.runCommand( { distinct: 'blogs', key: 'author'}) |
| Comment by Eliot Horowitz (Inactive) [ 21/May/11 ] |
|
In 1.9.0 the stats field in the distinct command result tells you which index was used if any. |