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

MySQL will not read TIME types on AWS Aurora with snapshot.fetch.size

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • Backlog
    • 2.7.3.Final, 3.0.1.Final
    • mysql-connector
    • None
    • False
    • None
    • False

      In MySQL, the notion of cursorFetch is directly associated with whether or not the user configures the snapshot.fetch.size connector configuration. The connector will use the text-based protocol to resolve temporal values when omitted. When provided, the connector uses the binary-based protocol.

      See https://debezium.zulipchat.com/#narrow/channel/302529-community-general/topic/MySQL.20TIME.20as.20duration/near/482350765

      I should note we had a similar situation when implementing MariaDB and we opted for MariaDB to simply have a singular text-based protocol implementation of the AbstractFieldReader contract.

              Unassigned Unassigned
              ccranfor@redhat.com Chris Cranford
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: