SAP HANA to Cassandra
real-time replication
TwinCommit replicates SAP HANA to Apache Cassandra in real time by reading the SAP HANA transaction log and applying every committed change exactly once and in commit order. Use it to serve SAP HANA data from Cassandra at scale without dual writes, with no triggers or capture tables on the source.
SAP HANA
log reader
commit-ordered · exactly-once
Cassandra
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 Cassandra
Batched upserts and deletes use the source commit timestamp as the Cassandra write timestamp, so replays are idempotent and newer data always wins.
Requirements
- ✓cdc_enabled: true in cassandra.yaml
- ✓WITH cdc = true on replicated tables
- ✓Agent sidecar or shared volume access to cdc_raw on each node
Setup
Set up SAP HANA → Cassandra 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 Cassandra
Add a target block for Cassandra. 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: cassandra
contact_points: [cass-1, cass-2, cass-3]
keyspace: replica
consistency: LOCAL_QUORUM
tables:
- source: SALES.ORDERS
- source: SALES.ORDER_LINES
exclude_columns: [INTERNAL_NOTES]SAP HANA to Cassandra replication FAQ
How does TwinCommit replicate SAP HANA to Cassandra?
+
TwinCommit reads changes from the SAP HANA transaction log, buffers them per transaction, and applies each committed transaction to Cassandra in commit order. Batched upserts and deletes use the source commit timestamp as the Cassandra write timestamp, so replays are idempotent and newer data always wins.
Does SAP HANA to Cassandra 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 Cassandra replication exactly-once?
+
Yes. TwinCommit commits its checkpoint in the same Cassandra 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 Cassandra today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.