Status: IN
Pipeline stages have fundamentally different resource profiles hidden behind a uniform tuple interface: Count is an unbounded memory barrier that materializes all input before emitting any output, Sort bounds memory via external merge-sort disk spillover, yet both produce and consume identical tuple lists with no way for the pipeline to distinguish streaming stages from blocking ones.
Uniform tuple interface hides asymmetric blocking and memory characteristics
Depends on (SL): count-is-barrier, sort-external-merge, pipeline-records-are-tuples