In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.

Bug report

For bug reports, provide this information, please:

What Debezium connector do you use and what version?

mysql connector version 1.9

What is the connector configuration?

debezium using Confluent Cloud and AWS Aurora 5.6 MySQL

What is the captured database version and mode of deployment?

AWS Aurora MySQL 5.6

What behaviour do you expect?

When the connector fails to write rows to the signal table on an incremental snapshot, the error message should provide the database error that was thrown and not the current generic error message

What behaviour do you see?

Database error while executing incremental snapshot for table '<table name>'

should see something to the effect of

Database error while executing incremental snapshot for table '<table name>' Database Error Message: <error message> Error Code: <error Code>

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

verified on 1.9 not sure of exact version

Do you have the connector logs, ideally from start till finish?

(You might be asked later to provide DEBUG/TRACE level log)

I do not

How to reproduce the issue using our tutorial deployment?

The tutorial project did not reproduce the error, in our case the error was caused by the fact that our connection did not have write permissions on the signal table.  The change I am hoping for is a more instructive error message to be returned