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

MariaDB connector documentation should make clear compressed logs are not supported

XMLWordPrintable

    • Informational

      Feature request or enhancement

      For feature requests or enhancements, provide this information, please:

      Which use case/requirement will be addressed by the proposed feature?

      The MariaDB connector version 3.1.2 does not support [binary log compression|https://mariadb.com/docs/server/server-management/server-monitoring-logs/binary-log/compressing-events-to-reduce-size-of-the-binary-log]. When compressed log entries are encountered by Debezium they are skipped.

      This limitation should be made explicit in the documentation, to save unnecessary debugging effort from developers.

      Implementation ideas (optional)

      The documentation should contain `log_bin_compress` in its MariaDB configuration examples:

       

      server-id                   = 223344
      log_bin                     = mariadb-bin
      log_bin_compress            = 0
      binlog_format               = ROW
      binlog_row_image            = FULL
      binlog_expire_logs_seconds  = 864000
      

      A warning box that contains the following would also be useful:

      IMPORTANT: The Debezium MariaDB connector currently does not support binary log compression. Make sure to set the MariaDB server configuration option `log_bin_compress` to `0` to ensure the connector can consume all events.

      I'm happy to send a pull request with the documentation updates.

       

              Unassigned Unassigned
              jschnab Jonathan Schnabel (Inactive)
              Jonathan Schnabel (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: