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

NULL Values are replaced by default values even in NULLABLE fields

    XMLWordPrintable

Details

    Description

      Hi,
      After the Debezium upgrade from 0.7.5 to 0.8.3.Final we see that NULL values are always converted to the field's default value, even if it's a nullable field.
      This behavior is incorrect, and causes wrong data to be sent to our consumer. We are using the MySql connector.
      These are the column we looked at from the table's definition in MySql:

      CREATE TABLE `campaign_ads` (
        `ad_id` int(11) NOT NULL,
       `max_cpc` float(20,8) DEFAULT '0.00000000',
        `max_cpm` float(20,8) DEFAULT '0.00000000',
        `max_cpc_in_target` float(20,8) DEFAULT '0.00000000',
        `max_cpm_in_target` float(20,8) DEFAULT '0.00000000',
        `cpa_goal_in_target` float(20,8) DEFAULT '0.00000000',
        `ocpm_actions` int(11) DEFAULT NULL,
        `ocpm_reach` int(11) DEFAULT NULL,
        `ocpm_clicks` int(11) DEFAULT NULL,
        `ocpm_social_imps` int(11) DEFAULT NULL,
        `budget` float(20,8) DEFAULT '0.00000000',
         PRIMARY KEY (`ad_id`)
       ) ENGINE=InnoDB DEFAULT CHARSET=utf8 ROW_FORMAT=COMPACT
      

      Example:
      We set the values of max_cpm to NULL, but in the Kafka topic the value was 0.0, which is the default value of this column.
      Please note that it is ok to set these values to NULL, as this column allows Nulls.

      Is it fixed in a later version?
      Are there any other issues between 0.7.5 to 0.8.3.Final we should be aware of?

      Thanks,
      Yifat Shani

      Attachments

        Issue Links

          Activity

            People

              jpechane Jiri Pechanec
              yifat.shani Yifat Shani (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: