[DOCS-168] Improved definitions of nscanned and nscannedobjects Created: 19/Mar/12 Updated: 14/Sep/12 Resolved: 14/Sep/12 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kyle Banker | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Days since reply: | 11 years, 48 weeks, 2 days ago | ||||||||||||||||
| Description |
|
The current definitions of, and distinctions between, nscanned and nscannedobjects are unclear: Can we get either better definitions, with examples, or perhaps more fields in the explain() output that can more clearly distinguish between the scanning of index keys, that of individual documents, etc.? |