[SERVER-5932] support cursor based aggregation Created: 25/May/12 Updated: 03/Jan/19 Resolved: 15/Jul/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | None |
| Fix Version/s: | 2.5.1 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Daniel Pasette (Inactive) | Assignee: | Mathias Stearn |
| Resolution: | Done | Votes: | 11 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
We should be able to get aggregation results out via a cursor as if they were a regular query. |
| Comments |
| Comment by Daniel Pasette (Inactive) [ 04/Sep/13 ] |
|
This feature is released on the dev branch. Initial documentation can be found here: http://docs.mongodb.org/manual/release-notes/2.6/#aggregation-operation-may-return-a-cursor |
| Comment by auto [ 08/Aug/13 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: Support cursors returned from sharded aggregation Follow-up to |
| Comment by auto [ 15/Jul/13 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: BuildBot ticket: |
| Comment by Eric Milkie [ 15/Jul/13 ] |
|
e.g. |
| Comment by Eric Milkie [ 15/Jul/13 ] |
|
Unit test is failing in debug mode |
| Comment by auto [ 11/Jul/13 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: related tickets: |
| Comment by auto [ 11/Jul/13 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: This is necessary for |
| Comment by Daniel Pasette (Inactive) [ 16/Jun/13 ] |
|
This is currently planned for the 2.6 release. |
| Comment by Bob Tiernay [ 15/May/13 ] |
|
This is crucial for any sizeable collection. Otherwise it may require reissuing the aggregation pipeline multiple times in order to page through the results. This is terribly inefficient. Is there an ETA on this feature? |