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

When updating mysql connector from 1.9 to 2.3, it asks for topic.prefix

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Major Major
    • None
    • None
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • False

      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:

      Cannot successfully update MySQL Debezium connector, don't know what to set in field topic.prefix

      What Debezium connector do you use and what version?

      Trying update from 1.9.7 to 2.3

      What is the connector configuration?

       connector.class = io.debezium.connector.mysql.MySqlConnector
       database.history.file.filename = data/db-history.dat
       database.user = xxx_production
       transforms.singleTopic.topic.regex = ([^.]+).*
       transforms = singleTopic
       database.server.name = debezium_mysql_xxxxx
       transforms.singleTopic.type = io.debezium.transforms.ByLogicalTableRouter
       transforms.singleTopic.topic.replacement = $1
       database.port = 3306
       tombstones.on.delete = false
       offset.storage.file.filename = data/offsets.dat
       database.hostname = 127.0.0.1
       database.password = ********
       name = pubsub
       database.history.skip.unparseable.ddl = true
       database.history = io.debezium.relational.history.FileDatabaseHistory
       database.include.list = xxx_production

      What is the captured database version and mode of depoyment?

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

      Kubernetes deployment in GKE cluster

      What behaviour do you expect?

      Successful update

      What behaviour do you see?

      Failed with error about topic.prefix (need it)

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

      (Ideally, also verify with latest Alpha/Beta/CR version)

      Trying to update to the latest

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

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

      Right now don't have, as rollback to old version

      How to reproduce the issue using our tutorial deployment?

      <Your answer>

      Feature request or enhancement

      For feature requests or enhancements, provide this information, please:

      Which use case/requirement will be addressed by the proposed feature?

      <Your answer>

      Implementation ideas (optional)

      <Your answer>

              Unassigned Unassigned
              arnikasky@gmail.com Hanna Novikava (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: