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

SQL Server Signal table Id mismatch

XMLWordPrintable

    • False
    • Hide

      None

      Show
      None
    • False
    • Moderate

      What Debezium connector do you use and what version?

      I'm using the SQL Server Connector version 3.0.6

      What behavior do you expect?

      When the Signal table have a 'uniqueidentifier' Id type the request should match the one from the Kafka topic.

      What behavior do you see?

      What happens is the window is ignored due to casing with the message: 

      Received request to open window with id = '691816A5-9E71-4BCB-9569-9D679E09E47B', expected = '691816a5-9e71-4bcb-9569-9d679e09e47b', request ignored
      
       Received request to close window with id = '691816A5-9E71-4BCB-9569-9D679E09E47B', expected = '691816a5-9e71-4bcb-9569-9d679e09e47b', request ignored

      A workaround is to use another column type, but even after changing the column type new incremental requests do not work (this may be due offsets).

      Do you see the same behaviour using the latest released Debezium version?

      Yes

       

              Unassigned Unassigned
              arielmoraes2 Ariel Moraes (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: