[SERVER-20744] Remove redundant code paths for setting a Value in a MutableDocument Created: 02/Oct/15  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: Aggregation Framework, Internal Code
Affects Version/s: 3.1.8
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Charlie Swanson Assignee: Backlog - Query Execution
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Query Execution
Backwards Compatibility: Fully Compatible
Participants:

 Description   

Currently there are a couple ways to set a field of a MutableDocument to a new value. The only one two that are move optimized are:

doc.getField(fieldName) = Value(val);
doc.getNestedField(fieldName) = Value(val);

We should remove all variants of MutableDocument::setField and MutableDocument::setNestedField in favor of the above strategy. We should also remove MutableDocument::getField in favor of MutableDocument::operator[]


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