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

debezium-examples fail when using confluentinc/cp-schema-registry:7.0.0

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Minor
    • 1.9.0.Alpha2
    • None
    • examples
    • None
    • False
    • False
    • Hide

       

      docker pull confluentinc/cp-schema-registry:7.0.0
docker-compose -f tutorials/docker-compose-mysql-avro-worker.yaml up

       

      Show
        docker pull confluentinc/cp-schema-registry:7.0.0 docker-compose -f tutorials/docker-compose-mysql-avro-worker.yaml up  

    Description

      The debezium-example tutorials that make use of schema-registry for avro schemas fail to start up with confluentinc/cp-schema-registry:7.0.0 which is being pulled in since the compose files uses latest tag. This is because the compose files are configuring the `kafkastore.connection.url` configuration which no longer supports schema-registry leader election in v7.0.0 and requires switching to `kafkastore.bootstrap.servers`

      Attachments

        Issue Links

          is related to

          Task - Represents a small unit of work that is not end-user facing. DBZ-4660 Remove legacy --zookeeper option from example instructions

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. DBZ-4660 Remove legacy --zookeeper option from example instructions

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Task - Represents a small unit of work that is not end-user facing. DBZ-4591 end-to-end example isn't working any longer

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Open

          Activity

            People

              Unassigned Unassigned
              eric-weaver Eric Weaver (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: