MySQL with binlog based sync fails with

io.debezium.DebeziumException: Error processing row in table, internal schema size 7, but row size 1 , restart connector with schema recovery mode.

Hmm, I don't know enough to give you a confident answer yet. The error message you're seeing suggests that there's a discrepancy between the internal schema size and the row size, and it recommends restarting the connector with schema recovery mode. However, the knowledge sources provided do not contain specific information or steps on how to resolve this particular issue. I recommend checking the [Airbyte documentation](https://docs.airbyte.io/) or the [Airbyte GitHub issues](https://github.com/airbytehq/airbyte/issues) for similar problems and their solutions. If you can't find a solution, consider opening a new issue on the GitHub page detailing your problem.

@kapa.ai List common MySql debezium related solutions. I think this error has something to do with later statements and schema not being up to date.

Based on the knowledge sources provided, there are a few common solutions and workarounds related to MySQL Debezium issues: 1. Downgrading the Debezium version: Some users have reported that downgrading the

source-mysql

to an older version (e.g., 3.1.1) solved their issue. This suggests that the problem might be related to a recent version upgrade of Debezium ([source](https://github.com/airbytehq/airbyte/issues/32348)). 2. Increasing the timeout: If you're experiencing issues with getting the schema history or if the process is timing out, you might want to consider increasing the timeout. If the issue persists, it might be a good idea to fail loud and clear, prompting the user to increase the timeout ([source](https://github.com/airbytehq/airbyte/issues/33107)). 3. Keeping Debezium state length constant: This solution involves keeping the Debezium state length constant regardless of the number of tables in the MySQL database. This can be tested by adding or deleting tables, CRUD on columns, and column datatypes ([source](https://github.com/airbytehq/airbyte/issues/28998)). Please note that these solutions are based on the information provided in the knowledge sources and might not cover all possible Debezium-related issues. If you're experiencing a specific issue not covered here, it might be helpful to look for more specific solutions or ask for help in the Debezium or Airbyte communities.

@kapa.ai Can I override this setting in the code props.setProperty("snapshot.locking.mode", "none"); by adding something to source connector settings or the connector settings?

A message from kapa.ai

If I want to change debezium settings, how do I do it? @kapa.ai

A message from kapa.ai