Avoid creating empty execution pipelines

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Query Execution
    • 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:
            Unassigned
            Reporter:
            Romans Kasperovics
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: