-
Bug
-
Resolution: Done
-
Major
-
2.3.0.Final, 2.3.2.Final
-
None
-
False
-
None
-
False
-
Important
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?
2.3.0.FINAL
What is the connector configuration?
{ "connector.class": "io.debezium.connector.mysql.MySqlConnector", "timezone": "GMT", "schema.history.internal.store.only.captured.databases.ddl": "false", "topic.prefix": "wave-mariadb", "schema.history.internal.kafka.topic": " wave-debezium-history", "value.converter": "org.apache.kafka.connect.json.JsonConverter", "key.converter": "org.apache.kafka.connect.json.JsonConverter", "database.user": "wave_debezium", "database.server.id": "3", "schema.history.internal.kafka.bootstrap.servers": "wave-kafka:9093", "schema.history.internal.skip.unparseable.ddl": "true", "database.port": "3306", "key.converter.schemas.enable": "false", "table.exclude.list": "wave.USER,wave.USER_PREFERENCES,wave.schema_version", "database.hostname": "wave-mysqldb", "database.password": "123456789", "name": "wave-debezium", "value.converter.schemas.enable": "true", "database.include.list": "health,wave", "snapshot.mode": "when_needed" }
What is the captured database version and mode of depoyment?
(E.g. on-premises, with a specific cloud provider, etc.)
on-premise 10.3.37
What behaviour do you expect?
Comment and DDL should be separated and behaved accordingly.
What behaviour do you see?
Both comment and DDL processed as comment. The DDL is below. All DDL file is skipped. Here is the DDL:
# Create the new ENTITY table which will be the parent of all other resource tables. CREATE TABLE IF NOT EXISTS ENTITY ( ID BIGINT AUTO_INCREMENT PRIMARY KEY, ENTITY_UUID VARCHAR(255) NOT NULL, ENTITY_TYPE VARCHAR(255) NULL, CREATED_ON DATETIME(6) NULL, UPDATED_ON DATETIME(6) NULL, CREATED_BY VARCHAR(255) NULL, UPDATED_BY VARCHAR(255) NULL, CONSTRAINT UI_NETWORK_ENTITY_UUID UNIQUE (ENTITY_UUID) );
Here is the log in debezium
2023-08-22 18:36:44,119 DEBUG | blc-wscp-mariadb-79871ae7:3306 | io.debezium.connector.mysql.MySqlStreamingChangeEventSource.handleQueryEvent(MySqlStreamingChangeEventSource.java:551)ogger{55} | Received query command: Event{header=EventHeaderV4
{timestamp=1692729344000, eventType=QUERY, serverId=2038897383, headerLength=19, dataLength=522, nextPosition=164399, flags=0}, data=QueryEventData{threadId=37, executionTime=0, errorCode=0, database='health', sql='# Create the new ENTITY table which will be the parent of all other resource tables.
CREATE TABLE IF NOT EXISTS NETWORK_ENTITY (
ID BIGINT AUTO_INCREMENT PRIMARY KEY,
ENTITY_UUID VARCHAR(255) NOT NULL,
ENTITY_TYPE VARCHAR(255) NULL,
CREATED_ON DATETIME(6) NULL,
UPDATED_ON DATETIME(6) NULL,
CREATED_BY VARCHAR(255) NULL,
UPDATED_BY VARCHAR(255) NULL,
CONSTRAINT UI_ENTITY_UUID UNIQUE (ENTITY_UUID)
)'}}
2023-08-22 18:36:44,119 DEBUG | blc-wave-mysqldb:3306 | io.debezium.connector.mysql.MySqlStreamingChangeEventSource.handleQueryEvent(MySqlStreamingChangeEventSource.java:578)ogger{55} | DDL '# Create the new ENTITY table which will be the parent of all other resource tables.
CREATE TABLE IF NOT EXISTS ENTITY (
ID BIGINT AUTO_INCREMENT PRIMARY KEY,
ENTITY_UUID VARCHAR(255) NOT NULL,
ENTITY_TYPE VARCHAR(255) NULL,
CREATED_ON DATETIME(6) NULL,
UPDATED_ON DATETIME(6) NULL,
CREATED_BY VARCHAR(255) NULL,
UPDATED_BY VARCHAR(255) NULL,
CONSTRAINT UI_ENTITY_UUID UNIQUE (ENTITY_UUID)
)' was filtered out of processing
Do you see the same behaviour using the latest relesead Debezium version?
(Ideally, also verify with latest Alpha/Beta/CR version)
2.3.2.Final also has same issue.
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?
Just run the connector
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>