SAP HANA to Kafka
real-time replication
TwinCommit replicates SAP HANA to Apache Kafka in real time by reading the SAP HANA transaction log and applying every committed change exactly once and in commit order. Use it to publish every committed SAP HANA change as an event stream, with no triggers or capture tables on the source.
SAP HANA
log reader
commit-ordered · exactly-once
Kafka
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 Kafka
Each source transaction is published with Kafka transactions, so consumers using read_committed never see a partial transaction. Messages are keyed by primary key in JSON, Avro or Protobuf.
Requirements
- ✓A topic naming template
- ✓Producer ACLs including transactional.id
- ✓Optional Schema Registry for Avro and Protobuf
Setup
Set up SAP HANA → Kafka 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 Kafka
Add a target block for Kafka. 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: kafka
bootstrap_servers: broker-1:9092,broker-2:9092
topic: "{schema}.{table}"
format: avro
schema_registry: http://registry:8081
tables:
- source: SALES.ORDERS
- source: SALES.ORDER_LINES
exclude_columns: [INTERNAL_NOTES]SAP HANA to Kafka replication FAQ
How does TwinCommit replicate SAP HANA to Kafka?
+
TwinCommit reads changes from the SAP HANA transaction log, buffers them per transaction, and applies each committed transaction to Kafka in commit order. Each source transaction is published with Kafka transactions, so consumers using read_committed never see a partial transaction. Messages are keyed by primary key in JSON, Avro or Protobuf.
Does SAP HANA to Kafka 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 Kafka replication exactly-once?
+
Yes. TwinCommit commits its checkpoint in the same Kafka 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 Kafka today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.