-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Query Integration
-
Fully Compatible
-
None
-
None
-
None
-
None
-
None
-
None
-
None
We should use the LiteParsedDesugarer instead of Desugarer, and we can remove Desugarer once we transition all desugaring call sites to the LiteParsedPipeline.
- depends on
-
SERVER-114802 Refactor extension LiteParsed to DocumentSource conversion
-
- Closed
-
-
SERVER-115055 Move query stats registration before view resolution
-
- Closed
-
-
SERVER-115330 Introduce LiteParsedDesugarer
-
- Closed
-
-
SERVER-116075 Add forQueryShapeOnly to expCtx
-
- Closed
-
-
SERVER-116269 Add isDesugared() to expCtx
-
- Closed
-
-
SERVER-116230 Overload DocumentSourceExtensionOptimizable create() to accept parseNode handle
-
- Closed
-
- is depended on by
-
SERVER-115066 Add view handling functions to LiteParsedPipeline
-
- Closed
-
-
SERVER-116234 Change DocumentSourceExtensionExpandable to DocumentSourceExtensionForQueryShape
-
- Closed
-
-
SERVER-115663 Merge DocumentSource::parse() and parseFromLiteParsed()
-
- Needs Scheduling
-
- related to
-
SERVER-115079 ResolvedView should fully desugar the view pipeline
-
- Closed
-
-
SERVER-115663 Merge DocumentSource::parse() and parseFromLiteParsed()
-
- Needs Scheduling
-
-
SERVER-116412 Refactor DocumentSourceChangeStream::createFromBson() to perform less work
-
- Needs Scheduling
-