-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Query Integration
-
None
-
0
-
None
-
None
-
None
-
None
-
None
-
None
Right now, we have a function search_helpers::addResolvedNamespaceForSearch() that adds the view information to the ExpressionContext only if it's a search query. I think it makes most sense to always add the view information to the ExpressionContext, particularly in case future devs want access to that information for some reason. We should remove this search-specific helper and have the run_agg path always include view information on the expCtx when applicable.
- is related to
-
SERVER-103684 Add separate API to ExpressionContext to hold view's ResolvedNamespace
-
- Closed
-