Uploaded image for project: 'Managed Service - Connectors'
  1. Managed Service - Connectors
  2. MGDCTRS-1878

Debezium SQL server and Mysql connector fixes

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Icon: Spike Spike
    • Resolution: Duplicate
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Very Likely
    • 0

      Based on discussion in https://chat.google.com/room/AAAA7ZWOryc/vZruVnBMPjk
       
       
       
      I just stumbled across this config in the debezium operator - https://github.com/bf2fc6cc711aee1a0c2a/cos-fleetshard/blob/1dbcf1737d49935e6ce9a6d54b2dd278ffa03563/cos-fleetshard-operator-debezium/src/main/java/org/bf2/cos/fleetshard/operator/debezium/DebeziumOperandController.java#L227 Just want to ask, whether this isn't actually replaced in the newer version with the schema.history.internal.kafka.bootstrap.servers, and want to ask, whether this shouldn't be handled on the debezium operator level, rather than by the connector properties. AFAIU, the database.history.kafka.bootstrap.servers is still configured by the operator, but is no longer needed in the newer version? The same for schema.history.internal.kafka.topic (might be wrong there however)

              rk3rn3r René Kerner
              tplevko@redhat.com Tomas Plevko
              Archiver:
              ranumula@redhat.com Raju Anumula

                Created:
                Updated:
                Resolved:
                Archived: