sure - I think, I explained the flushing behaviour in the class' JavaDoc
> 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 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]
