Skip to content
Replication route

MySQL to Hive
real-time replication

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

Hive

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
MySQL 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 MySQL → Hive in four steps

  1. 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. 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/mysql-to-apache-hive.yaml
source:
  type: mysql
  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]

MySQL to Hive replication FAQ

How does TwinCommit replicate MySQL to Hive?

+

TwinCommit reads changes from the MySQL 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 MySQL to Hive replication need triggers or capture tables?

+

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

Is MySQL 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 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 Hive today.

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