Remove sentinel primary and just use additional involved namespaces

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Integration
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Sentinel primary was used for backwards compatibility only in SPM-4532 and introduced by SERVER-124514 - but the "top-level namespace is or is not a view" semantic can be expressed by its presence in additionalResolvedNamespaces.

            Assignee:
            Unassigned
            Reporter:
            Finley Lau
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: