[DOCS-1918] Correction to "Pipeline Operators and Indexes" section in MongoDB documentation Created: 13/Sep/13  Updated: 11/Jan/17  Due: 20/Sep/13  Resolved: 17/Sep/13

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: None
Fix Version/s: 01112017-cleanup

Type: Bug Priority: Major - P3
Reporter: Jon Rangel (Inactive) Assignee: Sam Kleinman (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 10 years, 22 weeks, 1 day ago

 Description   

In the "Pipeline Operators and Indexes" section on the Aggregation Pipeline page (http://docs.mongodb.org/manual/core/aggregation-pipeline/), the following paragraph requires correction:

The $match, $sort, $limit, and $skip pipeline operators can take advantage of an index when they occur at the beginning of the pipeline or when they occur before the following aggregation operators: $project, $unwind, and $group.

should be changed to (changed text is in caps):

The $match, $sort, $limit, and $skip pipeline operators can take advantage of an index when they occur at the beginning of the pipeline AND when they occur before ANY OCCURRENCE OF the following aggregation operators: $project, $unwind, and $group.



 Comments   
Comment by auto [ 17/Sep/13 ]

Author:

{u'username': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}

Message: DOCS-1918: fix to clarify index use in aggregation pipelines
Branch: master
https://github.com/mongodb/docs/commit/abba7e0eb6a7d9f63e4454e0a9455aaf8b6a5334

Generated at Thu Feb 08 07:42:14 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.