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

Issue with Hybrid mode and DDL change

XMLWordPrintable

    • False
    • None
    • False
    • Critical

      In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.

      Bug report

      For bug reports, provide this information, please:

      What Debezium connector do you use and what version?

      Debezium Oracle Source Connector, version 2.6.1.Final

      What is the connector configuration?

      Attached in this file: config.txt

      What is the captured database version and mode of depoyment?

      (E.g. on-premises, with a specific cloud provider, etc.)

      Oracle, on-premises

      What behaviour do you expect?

      When Debezium Oracle connector use hybrid mode, it should add new column with default value to the topic from source replicated table

      What behaviour do you see?

      Connector fails with the following stacktrace: stacktrace.txt

      POLE2 is a column with default value, which is being added on source db. After adding it on source db, connector fails with attached error in stacktrace

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

      Yes, this behaviour repeats in latest released Debezium version

      Do you have the connector logs, ideally from start till finish?

      (You might be asked later to provide DEBUG/TRACE level log)

      Yes, in that file: stacktrace.txt . Unable to provide DEBUG / TRACE logs, sorry

      How to reproduce the issue using our tutorial deployment?

      Choose "log.mining.strategy": "hybrid" in connector configuration, and add in replicated table a column with default value

        1. config.txt
          2 kB
        2. stacktrace.txt
          18 kB

            vjuranek@redhat.com Vojtech Juranek
            steampart Andrey Romanov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: