Skip to content
Replication route

MariaDB to Hive
real-time replication

TwinCommit replicates MariaDB to Apache Hive in real time by reading the MariaDB transaction log and applying every committed change exactly once and in commit order. Use it to feed Hive 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

Hive

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
MariaDB source docs →

How apply works on Hive

Changes are written as ORC delta files and committed with Hive ACID MERGE, or as Iceberg snapshots through the Hive Metastore, depending on table format.

Requirements

  • ✓Transactional (ACID) tables or Iceberg tables
  • ✓HiveServer2 JDBC endpoint
  • ✓Write access to the warehouse location
Hive target docs →

Setup

Set up MariaDB → Hive in four steps

  1. 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. 2

    Point at Hive

    Add a target block for Hive. TwinCommit can generate target DDL with twincommit ddl -apply.

  3. 3

    Snapshot

    twincommit snapshot copies each table under a brief share lock and records the exact log position.

  4. 4

    Stream

    twincommit run streams every committed change from that position, exactly once and in commit order.

pipelines/mariadb-to-apache-hive.yaml
source:
  type: mariadb
  dsn: ${SOURCE_DSN}
  server_id: 4201

target:
  type: hive
  jdbc_url: jdbc:hive2://hs2.internal:10000/default
  table_format: iceberg

tables:
  - source: SALES.ORDERS
  - source: SALES.ORDER_LINES
    exclude_columns: [INTERNAL_NOTES]

MariaDB to Hive replication FAQ

How does TwinCommit replicate MariaDB to Hive?

+

TwinCommit reads changes from the MariaDB transaction log, buffers them per transaction, and applies each committed transaction to Hive in commit order. Changes are written as ORC delta files and committed with Hive ACID MERGE, or as Iceberg snapshots through the Hive Metastore, depending on table format.

Does MariaDB to Hive replication need triggers or capture tables?

+

No. TwinCommit reads the MariaDB log directly and creates no objects in the source database.

Is MariaDB to Hive replication exactly-once?

+

Yes. TwinCommit commits its checkpoint in the same Hive 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 Hive today.

Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.