Reference · built on requestConnectorDatabases & warehouses

MySQL

Tables, binary log row events, and document collections from MySQL over the client protocol and X DevAPI.

Request accessPricing ↗

About

MySQL is Oracle's open-source relational database. Clients reach it over TCP port 3306 with the MySQL client protocol, or over port 33060 through X Plugin, which is enabled by default in MySQL 8.4 and carries X Protocol for the X DevAPI. The server writes a binary log of data changes for replication and point-in-time recovery; in MySQL 8.4 the default format is ROW, so each event describes how individual table rows changed.

An operator on Fibric reads the tables you grant SELECT on, follows the binary log as a replica would, and proposes row changes for your approval. Each proposal carries a receipt: what changed, why, and how to undo it.

This is a reference listing. It documents what Fibric would read from MySQL and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Rows from tables the account can SELECT, read in batches by primary key or a timestamp column
  • Binary log row events (inserts, updates, deletes) requested with the REPLICATION SLAVE privilege, positioned by GTID
  • GTID sets from gtid_executed and gtid_purged, so a restart resumes from the last applied transaction
  • Binary log status through SHOW BINARY LOG STATUS and SHOW BINARY LOGS, granted by REPLICATION CLIENT
  • JSON documents in collections through X DevAPI over X Protocol on port 33060
  • Schema names visible to the account, listed with SHOW DATABASES

Proposed actions

  • Target capability: propose an INSERT or UPDATE statement against a table you name, run once after approval
  • Target capability: propose adding or modifying a document in an X DevAPI collection

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Watch order tables without polling

    Add the orders table to the connector, read row events from the binary log, and surface status changes shortly after they commit rather than on the next batch pull.

    With Order Risk, Data Freshness

  • Reconcile a dashboard figure against the source rows

    When a metric moves, read the underlying rows by primary key and show the reviewer which records account for the difference.

    With Metric Reconciliation, Operations Analyst

  • Notice when a feed goes stale

    Compare the newest timestamp in each watched table with the clock and flag tables that stop receiving writes.

    With Data Freshness

Requirements

  • A MySQL 8.4 server reachable on port 3306, or on port 33060 for X Protocol
  • An account with SELECT on the tables to read and SHOW DATABASES to list schemas
  • REPLICATION SLAVE and REPLICATION CLIENT privileges for reading binary log events and status
  • Binary logging on (log_bin=ON, the default) with binlog_format=ROW for row-level change events
Authentication
A MySQL account authenticated with caching_sha2_password, the MySQL 8.4 default, over a TLS connection or with RSA key-pair password exchange.

Limits

  • Statement-based binary log events carry SQL text, not row images; change capture needs events that were logged in ROW format
  • The server purges binary logs on its own schedule; transactions listed in gtid_purged can no longer be replayed
  • X Plugin accepts at most mysqlx_max_connections concurrent sessions, 100 by default
  • binlog_format is deprecated since MySQL 8.0, and Oracle expects row format to become the only logging format

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request MySQL ↗

Questions and answers

Does the connector need a replica or a replication user?
It reads the binary log the way a replica does, so the account needs REPLICATION SLAVE to request events and REPLICATION CLIENT to run SHOW BINARY LOG STATUS. No replica server is required; the connector connects to the source directly.
Which binary log format does change capture need?
ROW. MySQL 8.4 uses row-based logging by default, and each event records how individual table rows changed. Statement-based events carry SQL text instead of row images, which the connector cannot turn into before-and-after values.
What is X DevAPI and does the connector use it?
X DevAPI is the document-and-table API served by X Plugin over X Protocol on port 33060. X Plugin is enabled by default in MySQL 8.4. The connector can read JSON documents from collections through it; relational reads use the classic client protocol on port 3306.
Ask about MySQL

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with MySQL through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy