New feature
Public Preview
MySQL connector
MySQL connector is a Databricks data engineering capability, introduced December 2025.
A managed Lakeflow Connect database connector that incrementally ingests MySQL tables (RDS, Aurora, Azure, Cloud SQL, EC2) into Databricks by replaying the binary log through an ingestion gateway.
- Turn on PARTIAL_JSON binlog row values and any UPDATE to a JSON column makes the connector skip that whole table until you switch it off and run a full refresh.
- Its checkpoint is a binlog file name and position, which only means something on the server that wrote it - point the pipeline at another replica and the gateway refuses to resume until you refresh every table.
- In October 2026 MySQL also got an integrated CDC pipeline that needs no separate ingestion gateway, and it reached GA while the gateway-based connector docs still say Public Preview.
Limitations: The ingestion gateway runs continuously on classic compute (one gateway per pipeline), 250 or fewer tables per pipeline is recommended, spatial types and six character sets are not supported, MariaDB is not supported, Aurora read replicas cannot be used, and a purged binlog forces a full refresh (7 days of binlog retention recommended).
Open in REbricked →- Category
- Data engineering
- Also known as
- MySQL ingestion connector, Lakeflow Connect MySQL, MySQL CDC connector
- Verified
- 2026-10-20