-
Type:
Improvement
-
Resolution: Fixed
-
Priority:
Minor - P4
-
Affects Version/s: None
-
Component/s: None
-
Query Integration
-
Fully Compatible
-
None
-
None
-
None
-
None
-
None
-
None
-
None
There are various places throughout the codebase where we need the corresponding `LiteParsedPipeline` when resolving views. It would be beneficial to store this information directly in the `ResolvedNamespace` struct rather than recreating the pipeline object every time it's needed.
We should perhaps consider combining ResolvedNamespace, ResolvedView, and ViewInfo to reduce code complexity.
- depends on
-
SERVER-118963 Add ResolvedNamespacesMap to handleView()
-
- Closed
-
- related to
-
SERVER-122118 Remove ResolvedView in favor of ResolvedNamespace
-
- Needs Scheduling
-
-
SERVER-122119 Move public member variables in ResolvedNamespace to private member variables
-
- Needs Scheduling
-