Add separate API to ExpressionContext to hold view's ResolvedNamespace

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Integration
    • Fully Compatible
    • None
    • 3
    • None
    • 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.

            Assignee:
            Josh Siegel
            Reporter:
            Will Buerger
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: