Debezium Series: In-depth understanding of temporary blocking snapshots

1. Understanding temporary blocking snapshots

• Temporary blocking snapshots work similarly to temporary incremental snapshots; snapshots are still triggered by sending a signal to Debezium; however, the main difference is that while the connector handles the signal, streaming is put on hold while the snapshot process is running . This means you won't receive a series of read events intertwined with create, update, or delete events. This also means that we will process snapshots in a similar way to traditional snapshots, so throughput should generally be higher than incremental snapshots.
• Note that temporarily blocking snapshots pauses transaction log reading while the snapshot is taken. This means that the same requirements for transaction log availability of traditional snapshots apply when using this type of temporary snapshot mode. When the flow resumes, the connector will raise an error and stop if the required transaction log has been deleted.

The rate at which temporary blocking snapshots collect data is as follows:

2. Trigger temporary blocking snapshot

{
   
    
    
  "type"