On 20 June 2019, 16:36:09 -0600, Paul Gilmartin wrote:
> Im somewhat surprised. I had understood that Pipelines (usually)
> doesnt consume a record until something explicitly eats it.
Yes, the flow of records in the pipeline is well defined. Likely Glenn
was referring to UNIX that will buffer and arbitrary number of records.
This is more like my garden hose. The following should show me first and
and last record, but doesn't on my system today:
cat -n lazy.txt | { head -n 1; tail -n 1; }
I expect stages could even see part of a record as the first. I can't
really think how this would be useful. But no buffer is arbitrary too.
> In your example, what causes stage1, stage2, and stage3 to
> run consecutively rather than concurrently? Would FANIN rather
> than FANINANY make a difference?
And depending on how those stages deal with record delay, you may also
need to buffer before the FANIN.
Sir Rob the Plumber
