sure - I think, I explained the flushing behaviour in the class' JavaDoc
> Whenever {@link #add(BufferConsumer)} adds a finished {@link BufferConsumer}
> or a second {@link BufferConsumer} (in which case we will assume the first
> one finished), we will {@link PipelinedSubpartitionView#notifyDataAvailable()
> notify} a read view created via {@link
> #createReadView(BufferAvailabilityListener)} of new data availability. Except
> by calling {@link #flush()} explicitly, we always only notify when the first
> finished buffer turns up and then, the reader has to drain the buffers via
> {@link #pollBuffer()} until its return value shows no more buffers being
> available.
But it doesn't hurt to have something small / more explicit here as well
[ Full content available at: https://github.com/apache/flink/pull/6692 ]
This message was relayed via gitbox.apache.org for [email protected]
