[SERVER-46115] Implement 'let' parameters to aggregate commands Created: 12/Feb/20  Updated: 29/Oct/23  Resolved: 30/Apr/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.7.0

Type: Task Priority: Major - P3
Reporter: Jacob Evans Assignee: Eric Cox (Inactive)
Resolution: Fixed Votes: 0
Labels: qopt-team
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-46775 Use IDL to represent AggregationRequest Backlog
depends on SERVER-47191 Implement evalutation of Expressions ... Closed
is depended on by SERVER-46707 Support 'let' variables in aggregate ... Closed
is depended on by SERVER-46708 Support 'let' variables in update com... Closed
is depended on by DRIVERS-776 Support 'let' option for aggregate c... Closed
Documented
is documented by DOCS-13623 Investigate changes in SERVER-46115: ... Closed
Duplicate
is duplicated by SERVER-5192 Support variables in aggregation Closed
Issue split
split to SERVER-46998 Support 'let' variables used within $... Closed
Related
Backwards Compatibility: Fully Compatible
Sprint: Query 2020-03-09, Query 2020-04-06, Query 2020-04-20, Query 2020-05-04
Participants:

 Description   

See Scope document for syntax. The runtimeConstants mechanism is a suggested existing implementation.

For this ticket, we are only concerned with an implementation that works in unsharded deployments, and only for the aggregate command, and only for pipelines which don't use $merge. There is further work tracked in SERVER-46707 and SERVER-46998



 Comments   
Comment by Githook User [ 30/Apr/20 ]

Author:

{'name': 'Eric Cox', 'email': 'eric.cox@mongodb.com', 'username': 'ericox'}

Message: SERVER-46115 Implement 'let' parameters to aggregate commands
Branch: master
https://github.com/mongodb/mongo/commit/ef0e96cef56425a8d9ed23e98d79698260cb70c6

Comment by Eric Cox (Inactive) [ 30/Apr/20 ]

Code Review:

https://mongodbcr.appspot.com/584990004/

Generated at Thu Feb 08 05:10:32 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.