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

Using DBMS_LOB.ERASE by itself can lead to an unexpected UPDATE with null BLOB value

XMLWordPrintable

      The test OracleBlobDataTypesIT#shouldNotStreamAnyChangesWhenLobEraseIsDetected will actually randomly fail if the connector detects that a SourceRecord is emitted after the use of the DBMS_LOB.ERASE function block.

      The TransactionCommitConsumer creates a LobUnderConstruction instead but does not differentiate between actual NULL and not-provided, which causes the SELECT_LOB_LOCATOR to be emitted as an unintended UPDATE.

              ccranfor@redhat.com Chris Cranford
              ccranfor@redhat.com Chris Cranford
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: