-
Bug
-
Resolution: Unresolved
-
Major
-
2.4.0.Alpha2
-
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?
debezium2.4 alpha2
What is the connector configuration?
"config": {
"topic.prefix" : "servertest2",
"connector.class" : "io.debezium.connector.oracle.OracleConnector",
"tasks.max" : "1",
"database.hostname" : "xx",
"database.port" : "xx",
"database.user" : "xx",
"database.password" : "xx",
"database.dbname" : "xx",
"schema.history.internal.kafka.bootstrap.servers" : "172.19.18.138:9092",
"schema.history.internal.kafka.topic": "test.history",
"table.include.list":"TEST.NOINDEX",
"snapshot.mode" : "initial",
"snapshot.locking.mode":"none",
"tombstones.on.delete": "false",
"event.processing.failure.handling.mode": "skip",
"decimal.handling.mode" : "double",
"database.history.skip.unparseable.ddl": "true",
"database.history.store.only.captured.tables.ddl": "true",
"database.connection.adapter": "logminer",
"database.tablename.case.insensitive": "true",
"log.mining.strategy": "online_catalog",
"lob.enabled": "false",
"transforms":"Reroute",
"transforms.Reroute.type":"io.debezium.transforms.ByLogicalTableRouter",
"transforms.Reroute.topic.regex":"(.*)",
"transforms.Reroute.topic.replacement":"test"
}
What is the captured database version and mode of depoyment?
oracle 19c
What behaviour do you expect?
After the primary key is deleted, the collected data key is empty
What behaviour do you see?
After the primary key is deleted, the deleted primary key is still displayed in the collected data
Do you see the same behaviour using the latest relesead Debezium version?
In version 1.9 of Debezium. this phenomenon also occurs
Implementation ideas (optional)
If the primary key is empty, the key of the collected data is empty
