[DOCS-8779] $all now choose optimal condition not the first one Created: 07/Sep/16 Updated: 09/Nov/16 Resolved: 09/Nov/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Server |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Yaoxing Zhang | Assignee: | Steve Renaker (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 7 years, 14 weeks, 1 day ago | ||||||||
| Story Points: | 0.5 | ||||||||
| Description |
|
https://docs.mongodb.com/manual/reference/operator/query/all/#performance
With |
| Comments |
| Comment by Githook User [ 09/Nov/16 ] |
|
Author: {u'username': u'steveren', u'name': u'Steve Renaker', u'email': u'steve.renaker@mongodb.com'}Message: Signed-off-by: kay <kay.kim@10gen.com> |
| Comment by David Storch [ 16/Sep/16 ] |
|
ravind.kumar, it's probably sufficient to just delete it. This note is indeed out of date for all 3.2.x versions, as well as later patch releases of 2.6 and 3.0. If you were to replace it with anything, you could describe the new planning behavior introduced in |
| Comment by Ravind Kumar (Inactive) [ 16/Sep/16 ] |
|
david.storch looking at |