Skip to content
Replication route

PostgreSQL to Hive
real-time replication

TwinCommit replicates PostgreSQL to Apache Hive in real time by reading the PostgreSQL transaction log and applying every committed change exactly once and in commit order. Use it to feed Hive with live PostgreSQL data for analytics, AI and reporting, with no triggers or capture tables on the source.

PostgreSQL

log reader

commit-ordered · exactly-once

Hive

native writer

How capture works on PostgreSQL

TwinCommit uses a logical replication slot with the built-in pgoutput plugin, so there is nothing to install on the server.

Prerequisites

  • ✓wal_level = logical
  • ✓REPLICATION privilege
  • ✓Primary key or REPLICA IDENTITY FULL
PostgreSQL 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 PostgreSQL → Hive in four steps

  1. 1

    Prepare PostgreSQL

    Run twincommit check. It verifies wal_level = logical 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/postgresql-to-apache-hive.yaml
source:
  type: postgres
  dsn: ${SOURCE_DSN}
  slot: twincommit

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]

PostgreSQL to Hive replication FAQ

How does TwinCommit replicate PostgreSQL to Hive?

+

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

+

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

Is PostgreSQL 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 PostgreSQL versions are supported?

+

PostgreSQL 13–18 · Amazon RDS and Aurora · Azure Flexible Server · Cloud SQL · AlloyDB.

Stream PostgreSQL to Hive today.

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