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

Re-select columns should use the table's primary instead of the event's key

    XMLWordPrintable

Details

    Description

      What Debezium connector do you use and what version?

      2.5.0.Final

      What is the connector configuration?

      "post.processors": "reselector", 
        "reselector.type": "io.debezium.processors.reselect.ReselectColumnsPostProcessor", 
        "reselector.reselect.columns.include.list": "ASEDBUSR.FDOSSDECKPARAMATTR:TEXTVALUE,ASEDBUSR.FDOSSDECKPARAMATTR:BIGTEXTVALUE", 
        "reselector.reselect.unavailable.values": "true", 
        "reselector.reselect.null.values": "true"

      What is the captured database version and mode of depoyment?

      Oracle 19c on prem CDB

      What behaviour do you expect?

      Re-selection should get the most current state of the source record based on the table's primary key and not based on the event's key 

      What behavioyur do you see?

      Re-selection detected multiple rows for the same key in table ASEX92A.ASEDBUSR.FDOSSDECKPARAMATTR, using first

       

      Attachments

        Issue Links

          Activity

            People

              ccranfor@redhat.com Chris Cranford
              renerh René Rütter
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: