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

Provide first class support for MariaDB

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Major
    • 2.5.0.Alpha1
    • 1.7.0.CR1
    • mysql-connector
    • None
    • False
    • False
    • 0
    • 0% 0%
    • Undefined

    Description

      MariaDB starts to diverge from MySQL in a significant amount of fetaures. Right know we support MariaDB on best effort basis but we should support it fully. For thea purpose we need to

      • Modify binary log client to be compatible with MariaDB
      • Add missing features to it
      • Decide whether we will introduce a new connector ar MySQL connector will support both configs

      Attachments

        Issue Links

          causes

          Bug - A problem that impairs or prevents the functions of the product. DBZ-7121 XA transactions on MariaDB prevent streaming

          • 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
          is related 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-2499 Debezium Connectors are failing while reading binlog: Unknown event type 100

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

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) DBZ-2524 Ignore proprietary binlog extensions

          • 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
              jpechane Jiri Pechanec
              Votes:
              3 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: