MariaDB to Spark
real-time replication
TwinCommit replicates MariaDB to Apache Spark in real time by reading the MariaDB transaction log and applying every committed change exactly once and in commit order. Use it to process every committed MariaDB change in real time with Spark, with no triggers or capture tables on the source.
MariaDB
log reader
commit-ordered · exactly-once
Spark
native writer
How capture works on MariaDB
TwinCommit reads the row-based binary log as a replica using MariaDB GTIDs, and follows Galera cluster failover automatically.
Prerequisites
- ✓binlog_format = ROW and binlog_row_image = FULL
- ✓REPLICATION SLAVE and BINLOG MONITOR grants
- ✓log_slave_updates on Galera nodes
How apply works on Spark
The TwinCommit Spark connector exposes each pipeline as a Structured Streaming source with offsets mapped to log positions, so your jobs get exactly-once semantics with Spark checkpoints.
Requirements
- ✓The twincommit-spark connector JAR on the driver class path
- ✓Network access from the driver to the TwinCommit change feed endpoint
Setup
Set up MariaDB → Spark in four steps
- 1
Prepare MariaDB
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 Spark
Add a target block for Spark. 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: mariadb
dsn: ${SOURCE_DSN}
server_id: 4201
target:
type: spark
listen: 0.0.0.0:7443
tls: true
tables:
- source: SALES.ORDERS
- source: SALES.ORDER_LINES
exclude_columns: [INTERNAL_NOTES]MariaDB to Spark replication FAQ
How does TwinCommit replicate MariaDB to Spark?
+
TwinCommit reads changes from the MariaDB transaction log, buffers them per transaction, and applies each committed transaction to Spark in commit order. The TwinCommit Spark connector exposes each pipeline as a Structured Streaming source with offsets mapped to log positions, so your jobs get exactly-once semantics with Spark checkpoints.
Does MariaDB to Spark replication need triggers or capture tables?
+
No. TwinCommit reads the MariaDB log directly and creates no objects in the source database.
Is MariaDB to Spark replication exactly-once?
+
Yes. TwinCommit commits its checkpoint in the same Spark transaction as the data, so a crash or restart never loses or duplicates a transaction.
What MariaDB versions are supported?
+
MariaDB 10.6, 10.11, 11.x · Galera Cluster · SkySQL · Amazon RDS for MariaDB.
Stream MariaDB to Spark today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.