Skip to content
Replication route

SAP HANA to Hive
real-time replication

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

SAP HANA

log reader

commit-ordered · exactly-once

Hive

native writer

How capture works on SAP HANA

TwinCommit reads the SAP HANA redo log through a log-reader technical user and decodes row and column-store changes, with no triggers or shadow tables in your SAP schema.

Prerequisites

  • ✓log_mode = normal
  • ✓Technical user with LOG ADMIN and CATALOG READ
  • ✓Primary keys on replicated tables
SAP HANA 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 SAP HANA → Hive in four steps

  1. 1

    Prepare SAP HANA

    Run twincommit check. It verifies log_mode = normal 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/sap-hana-to-apache-hive.yaml
source:
  type: saphana
  host: hana.internal:30015
  user: ${HANA_USER}
  password: ${HANA_PASSWORD}

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]

SAP HANA to Hive replication FAQ

How does TwinCommit replicate SAP HANA to Hive?

+

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

+

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

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

+

SAP HANA 2.0 SPS05+ · SAP HANA Cloud · S/4HANA and BW/4HANA schemas.

Stream SAP HANA to Hive today.

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