-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Query Planning
-
None
-
Query Optimization
-
ALL
-
Query Optimization 2021-05-17, Query Optimization 2021-05-31, Query Optimization 2021-06-14, Query Optimization 2021-06-28, Query Optimization 2021-07-12, Query Optimization 2021-07-26, QO 2021-09-06, Query Optimization 2021-08-09, QO 2021-09-20, QO 2021-10-04, QO 2021-08-23
Upon inspecting a unit test we recently discovered that the server's logic for analyzing modified and renamed paths seems to mistakenly mark a rename from "x" to "y" like {$set: {y: "$x"}} as only renaming, whereas it should also mark "y" as modified since the old value is getting overridden.
- related to
-
SERVER-93675 Address $addFields renamedPaths() behaviour
- Closed