Ensure QueryKnobConfiguration values can be accessed in DocumentSource::optimize()

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution
    • QE 2026-04-13
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Initializing the query knob configurator in doOptimize() causes a tassert for queries containing sub-pipeline stages (e.g. $unionWith). When the ExpressionContext is copied for the sub-pipeline, query settings are applied after the configurator has already been initialized, violating the expected dependency order.

            Assignee:
            Unassigned
            Reporter:
            Catalin Sumanaru
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: