-
Bug
-
Resolution: Unresolved
-
Major
-
2.7.2.Final
-
None
-
2
-
False
-
None
-
False
-
Important
Bug report
For bug reports, provide this information, please:
What Debezium connector do you use and what version?
Debezium MariaDB Connector, the version is 2.7.2
What is the connector configuration?
{
"connector.class": "io.debezium.connector.mariadb.MariaDbConnector",
"database.hostname": "my-database-host",
"database.include.list": "my_database",
"database.password": "mypassword",
"database.port": "3306",
"database.server.id": "12345",
"database.ssl.mode": "disabled",
"database.user": "debezium",
"errors.log.enable": "true",
"include.schema.changes": "true",
"internal.key.converter": "org.apache.kafka.connect.json.JsonConverter",
"internal.value.converter": "org.apache.kafka.connect.json.JsonConverter",
"key.converter": "io.confluent.connect.avro.AvroConverter",
"key.converter.schema.registry.url": "http://kafka-schema-registry:8081",
"name": "kafka-mariadb-connector",
"sasl.jaas.config": "org.apache.kafka.common.security.plain.PlainLoginModule required username=\"kafka\" password=\"kafka\";",
"sasl.mechanism": "PLAIN",
"schema.history.internal.consumer.sasl.jaas.config": "org.apache.kafka.common.security.plain.PlainLoginModule required username=\"kafka\" password=\"kafka\";",
"schema.history.internal.consumer.sasl.mechanism": "PLAIN",
"schema.history.internal.consumer.security.protocol": "SASL_PLAINTEXT",
"schema.history.internal.kafka.bootstrap.servers": "kafka:9092",
"schema.history.internal.kafka.topic": "schema-changes.inventory",
"schema.history.internal.producer.sasl.jaas.config": "org.apache.kafka.common.security.plain.PlainLoginModule required username=\"kafka\" password=\"kafka\";",
"schema.history.internal.producer.sasl.mechanism": "PLAIN",
"schema.history.internal.producer.security.protocol": "SASL_PLAINTEXT",
"schema.history.internal.store.only.captured.tables.ddl": "true",
"security.protocol": "SASL_PLAINTEXT",
"snapshot.locking.mode": "none",
"snapshot.mode": "no_data",
"table.include.list": "my_database.users, my_database.orders",
"tasks.max": "1",
"topic.prefix": "db",
"value.converter": "io.confluent.connect.avro.AvroConverter",
"value.converter.schema.registry.url": "http://kafka-schema-registry:8081"
}
What is the captured database version and mode of deployment?
(E.g. on-premises, with a specific cloud provider, etc.)
on-premises
What behavior do you expect?
The statements with INSERT/UPDATE operations with the UUID column should be processed successfully
What behavior do you see?
I see an error:
Caused by: io.debezium.DebeziumException: Error processing binlog event ... 7 more Caused by: io.debezium.text.ParsingException: DDL statement couldn't be parsed. Please open a Jira issue with the statement 'create table test_table_with_uuid( ID UUID null, name varchar(255) null)' no viable alternative at input 'create table test_table_with_uuid\n(\n ID UUID' at io.debezium.antlr.ParsingErrorListener.syntaxError(ParsingErrorListener.java:43) ...
Do you see the same behaviour using the latest released Debezium version?
(Ideally, also verify with latest Alpha/Beta/CR version)
Yes
Do you have the connector logs, ideally from start till finish?
(You might be asked later to provide DEBUG/TRACE level log)
No
How to reproduce the issue using our tutorial deployment?
Execute an SQL query on a database server:
CREATE TABLE test_table_with_uuid
(
id UUID NULL,
name VARCHAR(255) NULL
);
- relates to
-
-
- Closed
-