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?

debezium-connector-mysql-2.1.4.Final

What is the connector configuration?

"column.exclude.list" : "subscribers.subscriberdata.CardNumber",
"connector.class" : "io.debezium.connector.mysql.MySqlConnector",
"database.history.kafka.bootstrap.servers" : "localhost:9092",
"database.history.kafka.topic" : "cdc.topic.history",
"database.history.skip.unparseable.ddl" : "true",
"database.history.store.only.captured.tables.ddl" : "true",
"database.hostname" : "localhost",
"database.password" : "muizebed",
"database.port" : "3306",
"database.server.id" : "145",
"database.server.name" : "dev-jeff",
"database.user" : "debezium",
"include.schema.changes" : "false",
"inconsistent.schema.handling.mode" : "warn",
"name" : "source-mysql-cdc",
"schema.history.internal.kafka.bootstrap.servers" : "localhost:9092",
"schema.history.internal.kafka.topic" : "cdc.schema.history",
"snapshot.mode" : "initial",
"table.include.list" : "subscribers.subscriberdata,subscribers.SubscriberUserFields,subscribers.debezium_signal,configuration.Accounts",
"topic.prefix" : "cdc"
 

What is the captured database version and mode of depoyment?

(E.g. on-premises, with a specific cloud provider, etc.)

On-premises, MariaDB 10.6.10

What behaviour do you expect?

<Your answer>

What behaviour do you see?

Exception with shutdown of the producer:

[2023-04-12 16:16:20,889] ERROR [source-mysql-cdc|task-0] Producer failure (io.debezium.pipeline.ErrorHandler:38)
io.debezium.DebeziumException: io.debezium.text.ParsingException: DDL statement couldn't be parsed. Please open a Jira issue with the statement 'CREATE TABLE `EmailTemplates` (
  `EmailID` int(11) unsigned NOT NULL AUTO_INCREMENT,
  `AccountID` bigint(12) unsigned NOT NULL DEFAULT 0,
  `WebsiteTemplateTitle` varchar(100) NOT NULL,
  `Subject` varchar(128) NOT NULL,
  `MailBody` text NOT NULL,
  `MailHtmlBody` text DEFAULT NULL,
  PRIMARY KEY (`EmailID`),
  KEY `ixAccount` (`AccountID`) USING BTREE
) ENGINE=InnoDB AUTO_INCREMENT=5396 DEFAULT CHARSET=latin1 ROW_FORMAT=DYNAMIC WITH SYSTEM VERSIONING'
mismatched input 'WITH' expecting {<EOF>, '-'}
    at io.debezium.pipeline.source.AbstractSnapshotChangeEventSource.execute(AbstractSnapshotChangeEventSource.java:85)
    at io.debezium.pipeline.ChangeEventSourceCoordinator.doSnapshot(ChangeEventSourceCoordinator.java:155)
    at io.debezium.pipeline.ChangeEventSourceCoordinator.executeChangeEventSources(ChangeEventSourceCoordinator.java:137)
    at io.debezium.pipeline.ChangeEventSourceCoordinator.lambda$start$0(ChangeEventSourceCoordinator.java:109)
    at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
    at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
    at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
    at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
    at java.base/java.lang.Thread.run(Thread.java:829) 

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

(Ideally, also verify with latest Alpha/Beta/CR version)

<Your answer>

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

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

Yes

How to reproduce the issue using our tutorial deployment?

Not attempted

Feature request or enhancement

For feature requests or enhancements, provide this information, please:

Which use case/requirement will be addressed by the proposed feature?

<Your answer>

Implementation ideas (optional)

<Your answer>