MongoDB to Hive
real-time replication
TwinCommit replicates MongoDB to Apache Hive in real time by reading the MongoDB transaction log and applying every committed change exactly once and in commit order. Use it to feed Hive with live MongoDB data for analytics, AI and reporting, with no triggers or capture tables on the source.
MongoDB
log reader
commit-ordered · exactly-once
Hive
native writer
How capture works on MongoDB
TwinCommit opens change streams on replica sets and sharded clusters, persists resume tokens with the checkpoint, and keeps multi-document transactions intact.
Prerequisites
- ✓Replica set or sharded cluster (change streams need an oplog)
- ✓changeStream and find privileges on watched databases
- ✓Pre- and post-images enabled for full before/after values (optional)
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
Setup
Set up MongoDB → Hive in four steps
- 1
Prepare MongoDB
Run twincommit check. It verifies replica set or sharded cluster (change streams need an oplog) and the other prerequisites, and prints the exact fix for anything missing.
- 2
Point at Hive
Add a target block for Hive. 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: mongodb
uri: ${MONGODB_URI}
target:
type: hive
jdbc_url: jdbc:hive2://hs2.internal:10000/default
table_format: iceberg
tables:
- source: sales.orders
- source: sales.customersMongoDB to Hive replication FAQ
How does TwinCommit replicate MongoDB to Hive?
+
TwinCommit reads changes from the MongoDB 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 MongoDB to Hive replication need triggers or capture tables?
+
No. TwinCommit reads the MongoDB log directly and creates no objects in the source database.
Is MongoDB 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 MongoDB versions are supported?
+
MongoDB 5.0–8.x · MongoDB Atlas · replica sets and sharded clusters.
Stream MongoDB to Hive today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.