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

Introduce Pipeline::getNextResult() for call sites where Pipeline::getNext() cannot be used

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Minor - P4 Minor - P4
    • 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Query Execution
    • Fully Compatible
    • QE 2025-04-28
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, DocumentSourceExchange and DocumentSourceFacet do not use Pipeline::getNext() method to retrieve results from their sub-pipelines. This is because Pipeline::getNext() returns only the document being produced, while information about the execution of the Stage is also needed (pipeline->getSources().back()->getNext() satisfies this requirement).

      We therefore introduce Pipeline::getNextResult() as an inlined proxy for pipeline->getSources().back()->getNext() returning GetNextResult.

            Assignee:
            daniel.tabacaru@mongodb.com Daniel Tabacaru
            Reporter:
            romans.kasperovics@mongodb.com Romans Kasperovics
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: