-
Bug
-
Resolution: Done
-
Major
-
None
-
None
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.4.0.Alpha2
What is the connector configuration?
Source connector:
{ "name": "vk_nau25_src", "connector.class" : "io.debezium.connector.oracle.OracleConnector", "tasks.max" : "1", "database.hostname" : "***", "database.port" : "1521", "database.user" : "debezium", "database.password" : "***", "database.dbname": "NAUMENT1", "database.connection.adapter": "logminer", "schema.history.internal.kafka.topic": "vk_nau25_src.schema-changes", "schema.history.internal.kafka.bootstrap.servers": "broker1:29092,broker3:29092,broker3:29092", "schema.history.internal.store.only.captured.tables.ddl": "true", "schema.history.internal.store.only.captured.databases.ddl": "true", "value.converter": "io.confluent.connect.avro.AvroConverter", "value.converter.schema.registry.url": "http://naument-sr:8081", "key.converter": "io.confluent.connect.avro.AvroConverter", "key.converter.schema.registry.url": "http://naument-sr:8081", "errors.log.enable": "true", "snapshot.lock.timeout.ms":"5000", "include.schema.changes": "true", "snapshot.mode":"always", "decimal.handling.mode": "precise", "lob.enabled": "true", "datatype.propagate.source.type": ".*", "log.mining.session.max.ms": "120000",
"topic.prefix": "vk_nau25", "topic.creation.enable": "true", "topic.creation.default.partitions": "1", "topic.creation.default.include": "vk_nau25\\.*", "topic.creation.default.replication.factor": "1", "topic.creation.default.compression.type": "lz4", "topic.creation.default.retention.ms": "432000000", "table.include.list" : "DEBEZIUM.GBC_TBL_SERVICECALL_NC25"}
Sink connector
{ "name": "vk_nau25_sink", "connector.class": "io.debezium.connector.jdbc.JdbcSinkConnector", "connection.url": "jdbc:postgresql://***:5438/db_ods_test?currentSchema=naument1", "connection.username": "debeziumt", "connection.password": "***",
"auto.evolve": "true", "auto.create": "true", "tasks.max": "1", "topics.regex": "vk_nau25.DEBEZIUM.GBC_TBL_SERVICECALL_NC25", "table.name.format": "vk_nau25_tbl_servicecall", "insert.mode": "upsert", "delete.enabled": "true", "primary.key.mode": "record_key", "quote.identifiers": "true", "schema.evolution": "basic", "value.converter": "io.confluent.connect.avro.AvroConverter", "key.converter": "io.confluent.connect.avro.AvroConverter", "value.converter.schema.registry.url": "http://naument-sr:8081", "key.converter.schema.registry.url": "http://naument-sr:8081"}
Source table ddl (Oracle)
CREATE TABLE "DEBEZIUM"."GBC_TBL_SERVICECALL_NC25" ( "ID" NUMBER(19,0) NOT NULL ENABLE, "CREATION_DATE" TIMESTAMP (6) NOT NULL ENABLE, "CLAIM$TRANSFERDATE" DATE, "TITLE" VARCHAR2(4000 CHAR), "CLIENT_EMAIL" VARCHAR2(255 CHAR), PRIMARY KEY ("ID") USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 COMPUTE STATISTICS STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT) TABLESPACE "USERS" ENABLE ) SEGMENT CREATION IMMEDIATE;
Target table ddl (Postgres) - was created by debezium sink connector
CREATE TABLE naument1.vk_nau25_tbl_servicecall ( "ID" numeric(19) NOT NULL, "CREATION_DATE" timestamp(6) NOT NULL, "CLAIM$TRANSFERDATE" timestamp(6) NULL, "TITLE" varchar(4000) NULL, "CLIENT_EMAIL" varchar(255) NULL, CONSTRAINT vk_nau25_tbl_servicecall_pkey PRIMARY KEY ("ID") );
What is the captured database version and mode of depoyment?
(E.g. on-premises, with a specific cloud provider, etc.)
source db: Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production
target db:PostgreSQL 13.2 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 8.3.1 20191121 (Red Hat 8.3.1-5), 64-bit
What behaviour do you expect?
<Your answer>
What behaviour do you see?
sink connector fails with error:
Caused by: org.apache.kafka.connect.errors.DataException: CLAIM$TRANSFERDATE is not a valid field name at org.apache.kafka.connect.data.Struct.lookupField(Struct.java:254) at org.apache.kafka.connect.data.Struct.get(Struct.java:74) at io.debezium.connector.jdbc.dialect.GeneralDatabaseDialect.getColumnValueFromValueField(GeneralDatabaseDialect.java:653) at io.debezium.connector.jdbc.dialect.GeneralDatabaseDialect.columnQueryBindingFromField(GeneralDatabaseDialect.java:632) at io.debezium.connector.jdbc.dialect.postgres.PostgresDatabaseDialect.lambda$getUpsertStatement$1(PostgresDatabaseDialect.java:89) at io.debezium.connector.jdbc.dialect.SqlStatementBuilder.appendList(SqlStatementBuilder.java:37) at io.debezium.connector.jdbc.dialect.SqlStatementBuilder.appendLists(SqlStatementBuilder.java:55) at io.debezium.connector.jdbc.dialect.postgres.PostgresDatabaseDialect.getUpsertStatement(PostgresDatabaseDialect.java:89) at io.debezium.connector.jdbc.JdbcChangeEventSink.write(JdbcChangeEventSink.java:226) at io.debezium.connector.jdbc.JdbcChangeEventSink.execute(JdbcChangeEventSink.java:79)
Even though I can see that the table in target database was succesfully created, and it has a field "CLAIM$TRANSFERDATE".
Do you see the same behaviour using the latest relesead Debezium version?
(Ideally, also verify with latest Alpha/Beta/CR version)
2.4.0.Alpha2
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?
<Your answer>
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>
- links to
-
RHEA-2024:129636
Red Hat build of Debezium 2.5.4 release
