[SERVER-76326] Scrutinize DocumentSource parsers for representative query round-tripping Created: 19/Apr/23  Updated: 11/Oct/23  Resolved: 11/Oct/23

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

Type: Task Priority: Major - P3
Reporter: Charlie Swanson Assignee: Alyssa Clark
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-76330 Use representative query shape in que... Closed
is depended on by SERVER-85096 TRACKING: M3 Correctness Tickets Closed
Related
related to SERVER-81920 $merge serialization doesn't anonymiz... Closed
related to SERVER-76556 Scrutinize other parsers (Accumulator... Closed
is related to SERVER-76327 Scrutinize MatchExpression parser for... Closed
is related to SERVER-76328 Scrutinize expression parser for repr... Closed
Assigned Teams:
Query Integration
Backwards Compatibility: Fully Compatible
Sprint: QI 2023-10-16
Participants:

 Description   

Look through the parsing code (scattered throughout src/mongo/db/pipeline/document_source*) for any strict argument validation that might ruin the ability of a representative query shape to be re-parsed. There are some IDL files also.


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