Eighty-six DocumentSourceLookUp::_resolvedIntrospectionPipeline

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution
    • ALL
    • QE 2025-04-14, QE 2025-04-28, QE 2025-05-12, QE 2025-05-26, QE 2025-06-09, QE 2025-06-23, QE 2025-07-07
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      DocumentSourceLookUp builds a new executable pipeline for each document on the left side of the join. It also maintains _resolvedIntrospectionPipeline as a reference pipeline that is independent of any document.

      Managing this reference pipeline introduces difficult problems of ownership when detaching/reattaching op contexts and when executing a `dispose` operation that needs a valid op context. Additionally, the reference pipeline needs to stay in sync with changes in the BSON spec for the pipeline, which gets updated when resolving views, performing FLE rewrites, and optimizing the $lookup, which can be bug prone.

      Fortunately, VS Code includes the helpful Edit.LineDelete operation that can reliably eliminate any undesired behavior caused by _resolvedIntrospectionPipeline.

            Assignee:
            Justin Seyster
            Reporter:
            Justin Seyster
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: