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

Xstream support with LOB unavailable value placeholder support is inconsistent

    XMLWordPrintable

Details

    Description

      In DBZ-4276 we introduced unavailable.value.placeholder behavior and as a part of that we added some tests to deal with when LOB-support is disabled. There were some inconsistent behaviors when Xstream was being used that caused tests to fail because either the placeholder wasn't being emitted or the test made some poor assumptions about what Xstream state would be.

      1. Adjust tests to document the variances between LogMiner/Xstream and why
      2. Align Xstream unavailable value placeholder logic as close to LogMiner as possible
      3. Fix bug in before state of LOB values when using Xstream; this should always be the placeholder since Xstream cannot provide prior state for LOB columns.
      4. Schema changes for new but excluded tables could cause unexpected event dispatch.

      Attachments

        Issue Links

          relates to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) DBZ-4276 Support passing an unavailable placeholder value for CLOB/BLOB column types

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: