SAP HANA to Elasticsearch
real-time replication
TwinCommit replicates SAP HANA to Elasticsearch in real time by reading the SAP HANA transaction log and applying every committed change exactly once and in commit order. Use it to keep Elasticsearch search indexes current with SAP HANA, with no triggers or capture tables on the source.
SAP HANA
log reader
commit-ordered · exactly-once
Elasticsearch
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 Elasticsearch
Changes are sent through the _bulk API with the document ID set to the primary key and external versioning derived from the log position, so late or replayed writes can never overwrite newer data.
Requirements
- ✓An index template or mapping per table
- ✓API key with index and write privileges
- ✓TLS endpoint
Setup
Set up SAP HANA → Elasticsearch 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 Elasticsearch
Add a target block for Elasticsearch. 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: elasticsearch
url: https://search.internal:9200
api_key: ${ES_API_KEY}
index_template: "{schema}-{table}"
tables:
- source: SALES.ORDERS
- source: SALES.ORDER_LINES
exclude_columns: [INTERNAL_NOTES]SAP HANA to Elasticsearch replication FAQ
How does TwinCommit replicate SAP HANA to Elasticsearch?
+
TwinCommit reads changes from the SAP HANA transaction log, buffers them per transaction, and applies each committed transaction to Elasticsearch in commit order. Changes are sent through the _bulk API with the document ID set to the primary key and external versioning derived from the log position, so late or replayed writes can never overwrite newer data.
Does SAP HANA to Elasticsearch 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 Elasticsearch replication exactly-once?
+
Yes. TwinCommit commits its checkpoint in the same Elasticsearch 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 Elasticsearch today.
Download the free Developer edition, or have one of our replication engineers walk you through a migration plan.