[SERVER-69542] Refactor how we track metadata slots Created: 08/Sep/22  Updated: 08/Nov/22  Resolved: 08/Nov/22

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

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

Issue Links:
Depends
is depended on by SERVER-68517 Avoid object materialization for eval... Open
is depended on by SERVER-69543 Avoid object materialization in colum... Open
is depended on by SERVER-69647 Refactor how $group optimizes itself ... Closed
Duplicate
duplicates SERVER-60234 Implement plumbing for getField() pus... Closed
Sprint: QE 2022-09-19, QE 2022-10-03, QE 2022-10-31, QE 2022-11-14
Participants:

 Description   

In the SBE stage builder there is a map from string to slot ID used to track things like the recordId slot and the result object slot. This map is surprisingly also used in some places (and tempting to use in more) for some non metadata slots but rather slots which represent field paths. We should make it impossible to confuse these two.



 Comments   
Comment by Charlie Swanson [ 08/Nov/22 ]

This work was basically completed in a different way in SERVER-60234 (thanks andrew.paroski@mongodb.com!) so I'm closing this ticket as a duplicate

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