Bug report

In Version 2.5.4, there was no quotes for Number fields like this. for field 

ORDER_ID NUMBER(10,0) in ORDERS table

{"event_context":{"fc_name":"1234","table_n":"ORDERS","oper_type":"u","row_set":{"before":"{\"ORDER_ID\":666688,\..........

But, in Version 2.7.3, quotes are coming for this causing parsing errors

{"event_context":{"fc_name":"3735","table_n":"ORDERS","oper_type":"u","row_set":{"before":"{\"ORDER_ID\":\"147690\",\.............................

Is this expected in the newer version. If not, is there any settings to get it fixed.

What Debezium connector do you use and what version?

It is 2.7.3, but here are helpful additional library information we use in our Java Springboot application.

implementation 'io.debezium:debezium-api:2.7.3.Final'
implementation'io.debezium:debezium-embedded:2.7.3.Final'
implementation 'org.apache.kafka:connect-runtime:3.6.1'
implementation 'io.debezium:debezium-connector-oracle:2.7.3.Final'
implementation 'com.oracle.database.jdbc:ojdbc8:21.6.0.0'
implementation 'io.debezium:debezium-storage-kafka:2.7.3.Final'

What is the connector configuration?

connector:
decimalHandlingMode: string
name: <<NAME>>
class: io.debezium.connector.oracle.OracleConnector
offsetTopic: <<OFFSETTOPICNAME>>
offsetTopicNumberOfPartitions: 1
offsetTopicReplicationFactor: 1
heartbeatIntervalInMsecs: 100000
heartbeatQuery: SELECT * FROM MYTABLE WHERE ROWNUM <= 1

What is the captured database version and mode of deployment?

Data base in running on a data center and is an Oracle database of version 19c.

DB Server on Dev Database runs on a 2 node RAC. The Archived log files (which Log Miner reads from) are shared to both nodes in RAC as a shared path.

What behavior do you expect?

Was not expecting a quote for this. We do have decimalMode as string format, but that was only impacting decimal fields, not the non decimal fields like this.

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

Yes

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

I think just the snippet of the message I shared is enough.

How to reproduce the issue using our tutorial deployment?

Yes, please see bug report above.