MariaDB to BigQuery
real-time replication
TwinCommit replicates MariaDB to Google BigQuery in real time by reading the MariaDB transaction log and applying every committed change exactly once and in commit order. Use it to feed BigQuery with live MariaDB data for analytics, AI and reporting, with no triggers or capture tables on the source.
MariaDB
log reader
commit-ordered · exactly-once
BigQuery
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 BigQuery
Changes stream through the BigQuery Storage Write API into staging tables and are applied with MERGE on a configurable interval, so deletes and updates are reflected exactly.
Requirements
- ✓A service account with BigQuery Data Editor and Job User
- ✓A dataset for staging tables
- ✓Primary keys declared on target tables (recommended)
Setup
Set up MariaDB → BigQuery 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 BigQuery
Add a target block for BigQuery. 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: bigquery
project: acme-analytics
dataset: replica
credentials_file: /secrets/bq.json
tables:
- source: SALES.ORDERS
- source: SALES.ORDER_LINES
exclude_columns: [INTERNAL_NOTES]MariaDB to BigQuery replication FAQ
How does TwinCommit replicate MariaDB to BigQuery?
+
TwinCommit reads changes from the MariaDB transaction log, buffers them per transaction, and applies each committed transaction to BigQuery in commit order. Changes stream through the BigQuery Storage Write API into staging tables and are applied with MERGE on a configurable interval, so deletes and updates are reflected exactly.
Does MariaDB to BigQuery replication need triggers or capture tables?
+
No. TwinCommit reads the MariaDB log directly and creates no objects in the source database.
Is MariaDB to BigQuery replication exactly-once?
+
Yes. TwinCommit commits its checkpoint in the same BigQuery 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 BigQuery today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.