Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-94758

investigate whether it's inapproriate to use LiteParsedDocumentSourceDefault for DocSourceIdLookup

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

      SERVER-92918 is introducing a subpipeline and view namespace to DocSourceIdLookup. We will likely need a new LiteParsedDocumentSource<Type> to add additional authorization/validations. For instance, we don't want to support running $search queries on a view created with a $lookup pipeline because the $lookup could involve additional namespaces that wouldn't be reported by LiteParsedDocumentSourceDefault.

            Assignee:
            Unassigned Unassigned
            Reporter:
            maddie.zechar@mongodb.com Maddie Zechar
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: