[SERVER-77014] Make sure $project aggregation stage shapifies field paths properly Created: 10/May/23  Updated: 04/Oct/23  Resolved: 04/Oct/23

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

Type: Task Priority: Major - P3
Reporter: Will Buerger Assignee: Erin Zhu
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-85075 Tracking: Milestone 2 Closed
Assigned Teams:
Query Integration
Sprint: QO 2023-06-26, QO 2023-07-10, QO 2023-07-24, QO 2023-08-07, QO 2023-08-21, QO 2023-09-04, QO 2023-09-18
Participants:

 Description   

When we project a field path (e.g., {}{$project: {foo: "$bar"}}), it looks like it's shapifying to {$project: {HASH<foo>: true}} instead of {}{project: {HASH<foo>: "$HASH<bar>"}}. The weird thing is the tests in document_source_project_test all have it right.



 Comments   
Comment by Erin Zhu [ 04/Oct/23 ]

Tested projection with a field path in a pipeline and within a lookup pipeline. In both cases, the field path was correctly hashed. This error seems to have gone away! 

Comment by Charlie Swanson [ 20/Jul/23 ]

Returning to the backlog since naafiyan.ahmed@mongodb.com hasn't meaningfully started and is destined for other work soon

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