In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.

Bug report

I expect the AGE field to be null, but its actual value is the default value of 0 by default.

What Debezium connector do you use and what version?

debezium-oracle-connector.2.2.0.Final

What is the connector configuration?

name=oracle_logminer
database.connection.adapter=logminer
database.pdb.name=orclpdb1
connector.class=io.debezium.connector.oracle.OracleConnector
topic.prefix=oracle_logminer
snapshot.locking.mode=none
snapshot.mode=schema_only
log.mining.strategy=online_catalog
database.hostname=*...*
database.port=1521
database.user=c##ogg
database.password=******
database.dbname=orclcdb
schema.history.internal.store.only.captured.tables.ddl=true
schema.include.list=dw_user
key.converter.schemas.enable=false
value.converter.schemas.enable=false
table.include.list=dw_user.test,dw_user.test1
decimal.handling.mode=string
offset.storage", FlinkOffsetBackingStore.class.getCanonicalName());
offset.storage=org.apache.kafka.connect.storage.FileOffsetBackingStore
schema.history.internal", FlinkDatabaseHistory.class.getCanonicalName());

What is the captured database version and mode of depoyment?

oracle 19.0.0.0

What behaviour do you expect?

I expect the AGE field to be null, but its actual value is the default value of 0 by default.

What behaviour do you see?

I expect the AGE field to be null, but its actual value is the default value of 0 by default.

Do you see the same behaviour using the latest relesead Debezium version?

yes

Do you have the connector logs, ideally from start till finish?

{"before":null,"after":\{"ID":4,"NAME":"aaa","AGE":0}

,"source":

{"version":"2.2.0.Final","connector":"oracle","name":"oracle_logminer","ts_ms":1683512258000,"snapshot":"false","db":"ORCLPDB1","sequence":null,"schema":"DW_USER", "table":"TEST","txId":"09001500d1040000","scn":"18137395","commit_scn":"18137396","lcr_position":null,"rs_id":null,"ssn":0,"redo_thread":1,"user_name":"DW_USER"}

,"op":"c","ts_ms":1683512260612,"transaction":null}

How to reproduce the issue using our tutorial deployment?

DDL SQL: CREATE TABLE test(id NUMBER(2),name varchar2(100), age NUMBER(5) DEFAULT 0, PRIMARY KEY(id));

DML SQL: INSERT INTO test values(4,'aaa',null);

Note the age field with JSON record

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>