-
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
Each of these structures offers similar information, and it's unclear if there's a reason they needed to be differentiated, or if we just didn't consider sharing a common data structure. We should investigate removing SearchQueryViewSpec in favor of either ResolvedView or ResolvedNamespace; while we're at it, I'm curious if we could even consolidate ResolvedView/ResolvedNamespace into one structure. Perhaps that can be split off into another ticket. IDL could help consolidate here.
- is related to
-
SERVER-103684 Add separate API to ExpressionContext to hold view's ResolvedNamespace
-
- Closed
-
- related to
-
SERVER-103802 Make namespaces more clear in ExpressionContext and surrounding code
-
- Backlog
-