Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 8.3.0-rc0
Affects Version/s: None
Component/s: None
Labels:
- m1_desugar
- qi-extensions-api

Assigned Teams:

Query Integration
Backwards Compatibility:
Fully Compatible
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

Desugar extension stages need to be validated after the LiteParsedPipeline is created to ensure that they abide by the following constraints:
1. Cycle prevention: A stage must not transitively expand back into itself.
We will check per path by storing a stack of desugar stage names.

2. Bounded desugar depth (kMaxDesugarDepth = 10) per expansion path

We should create a structure similar to the ViewGraph that tracks a list of all seen desugar stage names, as well as increment a depth counter every time we go further down a nested desugaring path.

depends on

SERVER-109527 Create LiteParsedDocumentSourceExtension stubs

Closed

SERVER-109564 Modify ParseNode::expand() to return ExtensionContainer instead of a serialized pipeline

Closed

SERVER-110194 Return desugared pipeline as list of LiteParsedDocumentSource

Closed

SERVER-111605 Implement DocumentSourceExtension::LiteParsedExpandable & DocumentSourceExtension::LiteParsedExpanded

Closed

is depended on by

SERVER-112567 Create a shared expansion implementation between full parse and lite parse

Needs Scheduling

related to

SERVER-109780 Implement explicit desugaring step for Pipelines with Desugar Stages

In Code Review

(1 related to)

Assignee:: Lynne Wang
Reporter:: Lynne Wang
Participants:: Githook User, Lynne Wang
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Aug 20 2025 06:12:33 PM UTC
Updated:: Oct 16 2025 04:21:40 PM UTC
Resolved:: Oct 16 2025 04:21:40 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates