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

Upgrade Docker images to Kafka



    • Type: Enhancement
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 0.6
    • Component/s: None
    • Labels:


      The update should be seemless.

      An interesting improvement is better isolation between plug-ins for Kafka Connect. We'd have to adapt the set-up a bit to make use of the new "plugin.path" property and re-arrange the way our current connectors are put into archives. We agreed the simplest would be to have one fully independent plug-in per connector, i.e. the DBZ core JAR would be contained in each one of those. It means a bit of duplication, but makes things easier overall and the plug-ins truely independent, e.g. in terms of updates.

      One thing to keep in mind is implicitly created topics with a default replication factor of three which will break the tutorial as per Randall:

      I guess one thing to note when upgrading to The distributed worker now will create the topics used to store configs, offsets, and statuses. You can specify in the worker config the partition count and replication factor for each of those internal topics. However, the default for the replication factor is 3, which is good for production but means you need 3 brokers.

        Gliffy Diagrams


            Issue Links



                • Assignee:
                  jpechanec Jiri Pechanec
                  gunnar.morling Gunnar Morling
                • Votes:
                  0 Vote for this issue
                  3 Start watching this issue


                  • Created: