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

Support for mariadb GTID

    XMLWordPrintable

Details

    • Feature Request
    • Resolution: Done
    • Minor
    • 2.5.0.Beta1
    • 1.7.0.CR1
    • mysql-connector
    • None
    • 0
    • 0% 0%

    Description

      Kafka messages have
      ```
      "gtid": null
      ```
      when reading from mariadb database.

      Looking at https://github.com/debezium/debezium/blob/master/debezium-connector-mysql/src/main/java/io/debezium/connector/mysql/BinlogReader.java it seems that we are only supporting mysql style GTIDs. Otherwise, the integration seems to work.

      Is there any way to enable support for GTIDs in mariadb or is this a feature that needs to be implemented?

      Example snippet from `kafkacat`.

      "payload": {
      "before": null,
      "after":

      { "typeid": 21, "typename": "foo", "typecode": "bar3" }

      ,
      "source":

      { "version": "0.9.5.Final", "connector": "mysql", "name": "formbay", "server_id": 1, "ts_sec": 1568682452, "gtid": null, "file": "mysql-bin.000002", "pos": 740, "row": 0, "snapshot": false, "thread": 0, "db": "fb1", "table": "unittype", "query": null }

      ,
      "op": "c",
      "ts_ms": 1568682452788
      }

      Attachments

        Issue Links

          is duplicated by

          Enhancement - An enhancement or refactoring of existing functionality DBZ-7082 Support MariaDB's GTID implementation

          • 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-1145 Clarification on MySQL vs MariaDb Usage

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

          Bug - A problem which impairs or prevents the functions of the product. DBZ-5775 Read-Only implementation incremental snapshot does not work on MariaDB

          • 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

          Bug - A problem which 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.
          • Open
          relates to

          Feature Request - Feature requests from customers and/or users DBZ-2913 Provide first class support for MariaDB

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

          Activity

            People

              ccranfor@redhat.com Chris Cranford
              dlagos_formbay daniel lagos (Inactive)
              Votes:
              5 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: