Hi all,

I have a question regarding to the state checkpoint mechanism in Flink. I find 
the statement  "Once the last stream has received barrier n, the operator emits 
all pending outgoing records, and then emits snapshot n barriers itself” on the 
document 
https://ci.apache.org/projects/flink/flink-docs-master/internals/stream_checkpointing.html#exactly-once-vs-at-least-once
 
<https://ci.apache.org/projects/flink/flink-docs-master/internals/stream_checkpointing.html#exactly-once-vs-at-least-once>.

Does this mean that to achieve exactly-once semantic, instead of sending tuples 
downstream immediately the operator buffers its outgoing tuples in a pending 
queue until the current snapshot is committed? If yes, will this introduce 
significant processing delay?

Thanks,
Li

Reply via email to