SAP HANA to Spark
real-time replication
TwinCommit replicates SAP HANA to Apache Spark in real time by reading the SAP HANA transaction log and applying every committed change exactly once and in commit order. Use it to process every committed SAP HANA change in real time with Spark, with no triggers or capture tables on the source.
SAP HANA
log reader
commit-ordered · exactly-once
Spark
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
How apply works on Spark
The TwinCommit Spark connector exposes each pipeline as a Structured Streaming source with offsets mapped to log positions, so your jobs get exactly-once semantics with Spark checkpoints.
Requirements
- ✓The twincommit-spark connector JAR on the driver class path
- ✓Network access from the driver to the TwinCommit change feed endpoint
Setup
Set up SAP HANA → Spark in four steps
- 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
Point at Spark
Add a target block for Spark. 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: saphana
host: hana.internal:30015
user: ${HANA_USER}
password: ${HANA_PASSWORD}
target:
type: spark
listen: 0.0.0.0:7443
tls: true
tables:
- source: SALES.ORDERS
- source: SALES.ORDER_LINES
exclude_columns: [INTERNAL_NOTES]SAP HANA to Spark replication FAQ
How does TwinCommit replicate SAP HANA to Spark?
+
TwinCommit reads changes from the SAP HANA transaction log, buffers them per transaction, and applies each committed transaction to Spark in commit order. The TwinCommit Spark connector exposes each pipeline as a Structured Streaming source with offsets mapped to log positions, so your jobs get exactly-once semantics with Spark checkpoints.
Does SAP HANA to Spark 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 Spark replication exactly-once?
+
Yes. TwinCommit commits its checkpoint in the same Spark 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 Spark today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.