Uploaded image for project: 'Debezium'
  1. Debezium
  2. DBZ-8089

After changing the column datatype from int to float the Debezium fails to round it and i get a null value for this field in the stream

XMLWordPrintable

      1. Run alter table test modify salary float - the current data type is int
      2.  Run - insert into test values(1,12.46)                                                                   
      3.  When checking the stream, i see a null value  for that column and in the log there is an error message  -  "Failed to properly convert data value for 'ORCLPDB1.C##DBZUSER.TEST.SALARY' of type FLOAT: java.lang.ArithmeticException: Rounding necessary"

      Bug report

      For bug reports, provide this information, please:

      What Debezium connector do you use and what version?

      Oracle connector, version 2.6.0

      What is the connector configuration?

      ```

      debezium.sink.type=redis
      debezium.sink.redis.message.format=extended
      debezium.sink.redis.address=localhost:12001
      #debezium.sink.redis.password=Redis123
      debezium.sink.redis.memory.limit.mb=10000

      debezium.source.connector.class=io.debezium.connector.oracle.OracleConnector
      debezium.source.log.mining.strategy=online_catalog
      #debezium.source.log.mining.transaction.retention.ms=180000
      debezium.source.database.pdb.name=ORCLPDB1
      debezium.source.offset.storage=io.debezium.storage.redis.offset.RedisOffsetBackingStore
      debezium.source.topic.prefix=rdi
      debezium.source.database.dbname=ORCLCDB
      debezium.source.database.hostname=172.17.0.2
      debezium.source.database.port=1521
      debezium.source.database.user=c##dbzuser
      debezium.source.database.password=dbz
      debezium.source.include.schema.changes=false
      debezium.source.log.mining.query.filter.mode=in
      debezium.source.skip.messages.without.change=true
      debezium.source.table.include.list=C##DBZUSER.TEST
      debezium.source.offset.flush.interval.ms=1000
      debezium.source.tombstones.on.delete=false
      debezium.source.schema.history.internal=io.debezium.storage.redis.history.RedisSchemaHistory
      #debezium.source.internal.log.mining.read.only=true
      #debezium.source.schema.history.internal.store.only.captured.tables.ddl=true
      #debezium.source.log.mining.batch.size.min=100000
      #debezium.source.log.mining.batch.size.max=100000
      #debezium.source.log.mining.batch.size.default=100000
      #debezium.source.key.converter.schemas.enable=false
      #debezium.source.value.converter.schemas.enable=false
      debezium.source.decimal.handling.mode=double
      debezium.source.signal.data.collection=ORCLPDB1.C##DBZUSER.DEBEZIUM_SIGNAL

      debezium.transforms=AddPrefix
      debezium.transforms.AddPrefix.type=org.apache.kafka.connect.transforms.RegexRouter
      debezium.transforms.AddPrefix.regex=.*
      debezium.transforms.AddPrefix.replacement=data:$0
      #quarkus.log.category.*=TRACE
      #quarkus.log.category."io.debezium.connector.oracle.logminer.LogMinerHelper".level=TRACE

      1. The default minimum log level for every log category, change only quarkus.log.level when needed.
        quarkus.log.min-level=trace
      2. The default log level for every log category.
        quarkus.log.level=trace
      1. Determine whether to enable the JSON console formatting extension, which disables "normal" console formatting.
        quarkus.log.console.json=false
      2. The port on which Debezium exposes Microprofile Health endpoint and other exposed status information.

        What is the captured database version and mode of deployment?

      Oracle 19c

      What behavior do you expect?

      to get 12.46 for the salary field

      What behavior do you see?

      I get a null value for the salary field

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

      yes

       

      debez.log

              ccranfor@redhat.com Chris Cranford
              gali.levin gal levin (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: