[DOCS-8117] Deprecate single document aggregation result option Created: 16/Jun/16  Updated: 02/Nov/16  Resolved: 29/Sep/16

Status: Closed
Project: Documentation
Component/s: Server
Affects Version/s: None
Fix Version/s: 3.4.0

Type: Improvement Priority: Critical - P2
Reporter: Osmar Olivo Assignee: Kay Kim (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to DOCS-8666 3.4 Rel Notes: Deprecate agg command... Closed
is related to SERVER-24414 Deprecate not-cursor-based agg docume... Closed
Participants:
Days since reply: 7 years, 19 weeks, 6 days ago
Epic Link: 3.4 Agg/Arrays
Story Points: 0.25

 Description   

Prior to MongoDB 2.6, aggregation (without a $out stage) would return results as a single document. With MongoDB 2.6 we introduced a cursor-based interface and made this the default in both shell and drivers.

In 3.4 use of the not-cursor-based option is being deprecated



 Comments   
Comment by Githook User [ 29/Sep/16 ]

Author:

{u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}

Message: DOCS-8117 deprecate agg command w/o cursor
Branch: master
https://github.com/mongodb/docs/commit/fb3da578cfa775c25949993a7244f1053a3dcb68

Comment by David Storch [ 16/Jun/16 ]

Using an aggregation cursor should be a strict improvement over returning the results inside a single document. If the results fit inside a single 16MB BSONObj, then they can also be returned inside a single batch. In this case, no extra round-trip is required. If the results would not fit inside a single 16MB BSONObj, then aggregation cursors are required anyway. In addition, the client-side API for iterating the result set should be cleaner when using agg cursors.

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