MySQL to Databricks
real-time replication
TwinCommit replicates MySQL to Databricks in real time by reading the MySQL transaction log and applying every committed change exactly once and in commit order. Use it to feed Databricks with live MySQL data for analytics, AI and reporting, with no triggers or capture tables on the source.
MySQL
log reader
commit-ordered · exactly-once
Databricks
native writer
How capture works on MySQL
TwinCommit connects as a replica, reads the row-based binary log and tracks position by GTID, so failovers and replica promotions are seamless.
Prerequisites
- ✓binlog_format = ROW and binlog_row_image = FULL
- ✓GTID mode recommended
- ✓REPLICATION SLAVE and REPLICATION CLIENT grants
How apply works on Databricks
Micro-batches are staged as Parquet in your cloud storage and applied with Delta MERGE through a SQL warehouse. Deletes, updates and ordering are preserved per key.
Requirements
- ✓A SQL warehouse or all-purpose cluster
- ✓A Unity Catalog volume or external location for staging
- ✓A service principal with MODIFY on the target schema
Setup
Set up MySQL → Databricks in four steps
- 1
Prepare MySQL
Run twincommit check. It verifies binlog_format = row and binlog_row_image = full and the other prerequisites, and prints the exact fix for anything missing.
- 2
Point at Databricks
Add a target block for Databricks. TwinCommit can generate target DDL with twincommit ddl -apply.
- 3
Snapshot
twincommit snapshot copies each table under a brief share lock and records the exact log position.
- 4
Stream
twincommit run streams every committed change from that position, exactly once and in commit order.
source:
type: mysql
dsn: ${SOURCE_DSN}
server_id: 4201
target:
type: databricks
host: adb-1234567890.12.azuredatabricks.net
warehouse: replication-wh
catalog: main
schema: replica
tables:
- source: SALES.ORDERS
- source: SALES.ORDER_LINES
exclude_columns: [INTERNAL_NOTES]MySQL to Databricks replication FAQ
How does TwinCommit replicate MySQL to Databricks?
+
TwinCommit reads changes from the MySQL transaction log, buffers them per transaction, and applies each committed transaction to Databricks in commit order. Micro-batches are staged as Parquet in your cloud storage and applied with Delta MERGE through a SQL warehouse. Deletes, updates and ordering are preserved per key.
Does MySQL to Databricks replication need triggers or capture tables?
+
No. TwinCommit reads the MySQL log directly and creates no objects in the source database.
Is MySQL to Databricks replication exactly-once?
+
Yes. TwinCommit commits its checkpoint in the same Databricks transaction as the data, so a crash or restart never loses or duplicates a transaction.
What MySQL versions are supported?
+
MySQL 5.7, 8.0, 8.4, 9.x · Amazon RDS & Aurora MySQL · Azure Database for MySQL · Cloud SQL.
Stream MySQL to Databricks today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.