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

Move Pipeline::getNext() and Pipeline::getNextDocument() methods to agg::Pipeline()

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

      Move Pipeline::getNext() and Pipeline::getNextDocument() methods to agg::Pipeline().

      This implies replacing their call sites with agg::Pipeline()::getNext() and agg::Pipeline::getNextDocument(), which in turn implies that an instance of agg::Pipeline() is constructed using agg::buildPipeline() function before calling these methods.

      This change should be relatively small (affecting few dozens of call sites), because at this moment agg::Pipeline stages and Pipeline document sources are still the same objects.

      This ticket also implies removing Pipeline::stitch() methods, which will become redundant.

      We should re-run the performance comparison at this point.

            Assignee:
            Unassigned Unassigned
            Reporter:
            romans.kasperovics@mongodb.com Romans Kasperovics
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: