[SERVER-4436] Add support for tailable aggregation cursors Created: 06/Dec/11 Updated: 06/Dec/22 Resolved: 17/Jan/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Daniel Pasette (Inactive) | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Won't Fix | Votes: | 1 |
| Labels: | usability | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query
|
| Participants: |
| Description |
|
When we eventually provide aggregation in a non-command form, we should support tailable cursors, provided there aren't grouping/sorting functions in the pipeline (because those would require seeing the entire input dataset). As long as there aren't grouping operators, we can continue to provide results as find() does now. |
| Comments |
| Comment by Mathias Stearn [ 24/Aug/12 ] |
|
IIRC we only support tailable cursors on capped collections. That restriction would need to be lifted for this to be much use. |
| Comment by Chris Westin [ 14/Mar/12 ] |
|
If the grouping key has an index on it, we can make that tailable as well, because we'll be able to stream the groups as we see them. |