-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
False
-
None
-
False
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.Beta2 Oracle and jdbcSink
What is the connector configuration?
source:
{ "name": "vk_nau59_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_nau59_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_nau59", "topic.creation.enable": "true", "topic.creation.default.partitions": "1", "topic.creation.default.include": "vk_nau59\\.*", "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_NC59"}
sink:
{ "name": "vk_nau59_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_nau59.DEBEZIUM.GBC_TBL_SERVICECALL_NC59", "table.name.format": "vk_nau59_tbl_servicecall", "insert.mode": "upsert", "delete.enabled": "true", "primary.key.mode": "record_key", "quote.identifiers": "false", "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"}
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?
On source db (Oracle) I create table and insert a few rows there:
CREATE TABLE DEBEZIUM.GBC_TBL_SERVICECALL_NC59 ( 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), CLAIM_SUMRETURN FLOAT(126), ATTR$ATTR varchar2(30), PRIMARY KEY (ID) ); ALTER TABLE DEBEZIUM.GBC_TBL_SERVICECALL_NC59 ADD SUPPLEMENTAL LOG DATA (ALL) COLUMNS;INSERT INTO DEBEZIUM.GBC_TBL_SERVICECALL_NC59( ID, CREATION_DATE, CLAIM_TRANSFERDATE, TITLE, CLIENT_EMAIL, CLAIM_SUMRETURN) VALUES(1, SYSTIMESTAMP, SYSDATE, 'TITLE 1', 'EMAIL 1', 111.22); INSERT INTO DEBEZIUM.GBC_TBL_SERVICECALL_NC59( ID, CREATION_DATE, CLAIM_TRANSFERDATE, TITLE, CLIENT_EMAIL, CLAIM_SUMRETURN) VALUES(2, SYSTIMESTAMP, SYSDATE, 'TITLE 1', 'EMAIL 1', 111.22);INSERT INTO DEBEZIUM.GBC_TBL_SERVICECALL_NC59( ID, CREATION_DATE, CLAIM_TRANSFERDATE, TITLE, CLIENT_EMAIL, CLAIM_SUMRETURN) VALUES(3, SYSTIMESTAMP, SYSDATE, 'TITLE 1', 'EMAIL 1', 111.22);
Then I start source and sink connectors. Then I see that in the target db (Postgres) the table was created with not default but upper case of attribute ATTR$ATTR, I expect it to be lower. I guess it has sth to do with DBZ-6831.
ddl (table was created by debezium):
CREATE TABLE naument1.vk_nau59_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,
claim_sumreturn float8 NULL,
"ATTR$ATTR" varchar(30) NULL,
CONSTRAINT vk_nau59_tbl_servicecall_pkey PRIMARY KEY (id)
);
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)
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
