-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Minor - P4
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Integration
-
Fully Compatible
-
ALL
-
None
-
3
-
TBD
-
None
-
None
-
None
-
None
-
None
-
None
Currently, we are passing the underlying collection's NS to `buildPipelineFromViewDefinition()` as the `userNss`. This isn't correct as the `userNss` in this scenario is actually the `viewNs` while the `ResolvedNamespace` holds the underlying collection's NS.