[DOCS-960] Query optimizer behavior description incomplete and slightly misleading Created: 08/Jan/13 Updated: 14/Jan/13 Resolved: 11/Jan/13 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | Max Schireson | Assignee: | Kay Kim (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 11 years, 5 weeks, 2 days ago |
| Description |
|
Re: http://docs.mongodb.org/manual/core/read-operations/#query-optimization The optimizer iterates until it reaches 101 results from a single plan which is an ordered plan. It does not stop at 101 results if they are spread across multiple plans nornif the plan producing the results is an unordered plan. Thanks, – Max |
| Comments |
| Comment by auto [ 14/Jan/13 ] |
|
Author: {u'date': u'2013-01-14T18:08:24Z', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}Message: merge: |
| Comment by auto [ 14/Jan/13 ] |
|
Author: {u'date': u'2013-01-11T22:27:31Z', u'email': u'kay.kim@10gen.com', u'name': u'kay'}Message: |
| Comment by auto [ 14/Jan/13 ] |
|
Author: {u'date': u'2013-01-11T17:42:51Z', u'email': u'kay.kim@10gen.com', u'name': u'kay'}Message: |