Avoid creating empty execution pipelines

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: Query Execution
    • Query Execution
    • Fully Compatible
    • QE 2025-08-04
    • None
    • 3
    • TBD
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • 0

      Currently, we rely on the ability to create empty Pipeline instances in tests (and perhaps also productive code), and we have checks for emptiness in Pipeline::getNext() and Pipeline::getNextResult(), which is inefficient and increases code complexity. We should avoid creating empty execution pipelines (throw in exec::agg::Pipeline constructor) and remove emptyness check from other exec::agg::Pipeline methods.

              Assignee:
              Jan Steemann
              Reporter:
              Romans Kasperovics
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: