-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Integration
-
Fully Compatible
-
None
-
0
-
None
-
None
-
None
-
None
-
None
-
None
For $search queries run on a view, we currently add the view's resolved namespace to the ExpressionContext "resolvedNamespaces" map. However, the resolvedNamespaces map is intended to store foreign namespaces involved in the query, but not the primary namespace.
We should add a new API to hold the view's ResolvedNamespace separately from the foreign namespaces.
- is depended on by
-
SERVER-103944 Remove mongot/rankFusion-dependent logic for adding a view's ResolvedNamespace
-
- Backlog
-
-
SERVER-93539 Split AggExState into AggExState and ResolvedViewAggExState
-
- In Code Review
-
- related to
-
SERVER-103802 Make namespaces more clear in ExpressionContext and surrounding code
-
- Backlog
-
-
SERVER-103863 Always add the "view" information to expCtx
-
- Backlog
-
-
SERVER-103886 Investigate consolidating SearchQueryViewSpec with ResolvedView and/or ResolvedNamespace
-
- Backlog
-