Bug report

What Debezium connector do you use and what version?

MySQL, 3.0.

Bug present in earlier versions as well.

What behavior do you expect?

When the incremental snapshot pause signal is sent for a connector via Kafka, it should be saved to the connector offsets so that when the connector restarts it doesn't forget that the snapshots are paused. 

Furthermore, I (as the operator) should be able to pause snapshots even when they're not running. Effectively putting them on standby until I'm ready to run snapshots again.

The docs describing how to send the signal are misleading:

>The data field is ignored.

While the field is ignored, it still needs to be provided otherwise it causes a NullPointerException in the `KafkaSignalChannel` when it goes to `
data.toString()`, and the thread silently dies.
 
Finally, if the signal were properly saved, I would expect the `resume` signal to remove the flag that indicates that snapshots are paused.

What behavior do you see?

Nothing is saved in the connector offsets to indicate that the snapshot is paused. Restarting a connector will restart any paused snapshots.  

Do you see the same behaviour using the latest released Debezium version?

Yes