[DOCS-178] Make a note on the importance of order of operations in the aggregation "pipeline" Created: 29/Mar/12 Updated: 08/Sep/12 Resolved: 29/Mar/12 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Marc Bastien | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | aggregation | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 11 years, 46 weeks, 6 days ago |
| Description |
|
The current documentation does not adequately point out that the order of operations is critical when creating the "pipeline" array (placing $match before $group for example), and it has been a source of confusion. http://www.mongodb.org/display/DOCS/Aggregation+Framework#AggregationFramework-Invocation |
| Comments |
| Comment by Sam Kleinman (Inactive) [ 29/Mar/12 ] |
|
This issue is addressed more clearly in the manual <http://docs.mongodb.org/manual/applications/aggregation/#optimizing-performance>. |
| Comment by auto [ 29/Mar/12 ] |
|
Author: {u'login': u'tychoish', u'name': u'Sam Kleinman', u'email': u'samk@10gen.com'}Message: |