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

Clarification on MySQL vs MariaDb Usage

    XMLWordPrintable

Details

    Description

      Clarify if MariaDB can be used with Debezium right out of the box with customization. Is there a MariaDB connector that works, or must the MySQL connector be used with modifications?

      While MariaDB is meant to be a "drop in replacement" for MySQL, some core structures have diverged. The binlogging used by CDC is one such diversion.

      The Debezium blog post for Version 0.6 references MariaDB; "Finally, we’ve planned to test and adapt the existing MySQL connector for providing CDC functionality to MariaDB."

      There are multiple posts on the internet referencing using Debezium with MariaDB via the MySQL connector, but it is not clear if this actually works properly or if modifications to the connector are needed.

      Posting this information definitively on the Debezium site, the status of the MariaDB enhancements referenced in the blog post, and/or documentation in how to use the MySQL connector with MariaDB correctly would be extremely helpful for those working with MariaDB.

      Attachments

        Issue Links

          relates to

          Feature Request - Feature requests from customers and/or users DBZ-1482 Support for mariadb GTID

          • 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.
          • Resolved

          Feature Request - Feature requests from customers and/or users DBZ-2208 Support compressed binlog events from MariaDB

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Open

          Bug - A problem that impairs or prevents the functions of the product. DBZ-2291 Dummy event replacing event type 160 that slave cannot handle

          • 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

          Bug - A problem that impairs or prevents the functions of the product. DBZ-1476 MariaDB row level changes captured but not navigated to kafka

          • 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.
          • Open

          Activity

            People

              ccranfor@redhat.com Chris Cranford
              jziebro John Ziebro (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: