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

Revert Clob behavior for Oracle LogMiner to avoid null values

    XMLWordPrintable

Details

    Description

      In 1.4.1 , during an update statement the CLOB fields were passing through , but after upgrading to 1.4.2 I am seeing only null for the CLOB fields. The columns in the table are defined as NCLOB and that in 1.4.1 the values of those columns are coming in as strings.

      In 1.4.1

      UPDATE Table1
      SET INV_DESC = 'Test',
      WHERE ID = 123;
      
      "after”:\{“myTopic.Value":{"ID”:123,"INV_DESC":{"string":"Test"},
      

      In 1.4.2

      UPDATE Table1
      SET INV_DESC = 'Test2',
      WHERE ID = 123;
      
      "after”:{“myTopic.Value":{"ID”:123,"INV_DESC”:null,
      

      Attachments

        Issue Links

          Activity

            People

              ccranfor@redhat.com Chris Cranford
              shabinakareem Shabina Abdulkareem (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: