[DOCS-13620] Investigate changes in SERVER-46708: Support 'let' variables in update command Created: 28/Apr/20  Updated: 13/Nov/23  Resolved: 12/Nov/20

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 4.7.0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Jason Price
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-46708 Support 'let' variables in update com... Closed
Duplicate
is duplicated by DOCS-13636 Investigate changes in SERVER-46715: ... Closed
Participants:
Days since reply: 3 years, 13 weeks ago
Epic Link: DOCSP-9747
Story Points: 5

 Description   

Description

Downstream Change Summary

This patch allows users to specify let variables in update commands, through
both a top-level request parameter ('let') and a parameter ('c') for each update in the batch request. This currently focuses on unsharded deployments, with work on sharded environments to come in another ticket.

Description of Linked Ticket

Replace the 'runtimeConstants' support with the new 'let' syntax from the aggregate command in the update command. Similar to how that works, we should support both a top-level 'let' parameter to the update request and also a parameter for each update in the batch request. For now, let's stick with the name 'c' for the constants for each update in the batch, though we may revisit this name later.

Note that we will have to preserve support for 'runtimeConstants' for compatibility during upgrade. There will be a problem where an internal update request built on behalf of $merge will need to specify variables. This is done here. It's important for those variables/constants to be serialized as runtimeConstants, again for compatibility during upgrade. I would recommend making this work as part of this ticket, but if it becomes obvious how to split it into follow-up work we should do that.

For this work, focus only on unsharded deployments.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Githook User [ 11/Nov/20 ]

Author:

{'name': 'Jason Price', 'email': 'jason.price@mongodb.com', 'username': 'jason-price-mongodb'}

Message: DOCS-13620 Let variables in update
Branch: v5.0
https://github.com/mongodb/docs/commit/026715ece571e2ab88283992ac409fd32c6ffb3e

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