Skip to content
Data warehouse ⇄ Database

Apache Pinot to SAP Hana integration — real-time, two-way sync

Keep Apache Pinot and SAP Hana in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Apache Pinot and SAP Hana

Connect SAP Hana and Apache Pinot with one live, two-way sync: operational rows flow into the warehouse, and computed results flow back where systems can read them fast.

Operational databases and analytical warehouses want the same data at different moments. Analysts want SAP Hana's rows in Apache Pinot, current and joinable, without a change-data-capture pipeline to maintain. Engineers want the outputs of warehouse work, such as aggregates, features, and segments, available in SAP Hana where the services that read from it get them at normal query latency.

Stacksync covers both directions with one connection. Tables or collections in SAP Hana sync into Apache Pinot in real time, and result tables in Apache Pinot sync back into SAP Hana, with schema and type mapping between the two systems handled for you.

Common use cases

  • 01 Push reference and dimension data into Pinot via batch segment loads to enrich event queries.
  • 02 Sync Pinot aggregates into a warehouse to join low-latency metrics with modeled historical data.
  • 03 Read SYS.TABLES and TABLE_COLUMNS system views to auto-discover schema and generate field mappings when new tables are added to the sync.
  • 04 Detect inserts, updates, and deletes on high-write tables via AFTER triggers or a last-modified column and replicate the deltas downstream near-real-time.

Common sync patterns

Offload heavy reads

Point analytical queries at the synced copy in Apache Pinot and keep SAP Hana focused on its operational workload.

Operational data in the warehouse, minus the pipeline

Rows from SAP Hana land in Apache Pinot as they change, replacing hand-built CDC and batch extract jobs.

Serve warehouse results at database speed

Aggregates or model outputs computed in Apache Pinot sync into SAP Hana, where whatever reads from that database gets them without querying the warehouse.

What you can sync between Apache Pinot and SAP Hana

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Apache Pinot objects SAP Hana objects How this pairing syncs
Schemas Column definitions (dimensions, metrics, time columns) mapped during integration setup. Schemas Namespaces that group tables and views; the connector targets a schema and enumerates its objects from the catalog to build the sync. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Offline Tables Batch-loaded tables merged with real-time data at query time. Row store tables OLTP-oriented tables held fully in memory; read and written the same way through the SAP HANA client for high-write operational tables. Offline Tables is specific to Apache Pinot and Row store tables to SAP Hana — each maps to any object or custom field on the other side.
Indexes Inverted, range, and star-tree indexes that determine which sync queries run at low latency. Calculation views Modeled analytic views over base tables; read-only sources for pushing aggregated or joined results into a warehouse or downstream app. Indexes is specific to Apache Pinot and Calculation views to SAP Hana — each maps to any object or custom field on the other side.
Tenants Logical groupings that isolate workloads on shared clusters. SQL views Standard database views; read-only projections synced outbound when the source data should not be exposed as raw base tables. Tenants is specific to Apache Pinot and SQL views to SAP Hana — each maps to any object or custom field on the other side.
Tables The queryable unit, defined as offline, real-time, or hybrid; the main read target. Sequences Server-generated key values; relevant when writing rows into tables whose identity is assigned HANA-side rather than by the source system. Tables is specific to Apache Pinot and Sequences to SAP Hana — each maps to any object or custom field on the other side.
Segments Immutable data files that batch ingestion uploads and the cluster serves. Triggers AFTER INSERT/UPDATE/DELETE triggers capture changes into a shadow/logging table so updates and deletes are detected near-real-time without full scans. Segments is specific to Apache Pinot and Triggers to SAP Hana — each maps to any object or custom field on the other side.

How changes propagate between Apache Pinot and SAP Hana

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Apache Pinot SAP Hana Interval-based propagation

DetectionStacksync polls Apache Pinot for changes on an incremental schedule, reading only records changed since the previous pass. Data enters Pinot via streaming ingestion or segment upload, not row-level writes.

DeliveryEach detected change is applied to SAP Hana as a row-level write, with types converted between the two schemas.

SAP Hana Apache Pinot Sub-second propagation

DetectionChanges in SAP Hana are captured at the source via change data capture — no polling loop against its API. Polling on a last-modified timestamp column, or AFTER INSERT/UPDATE/DELETE triggers writing to a shadow table.

DeliveryEach detected change is applied to Apache Pinot as a row-level write, with types converted between the two schemas.

Rate-limit considerations

  • Apache Pinot: No fixed API quotas; query throughput depends on broker and server sizing.
  • SAP Hana: No SaaS-style request quota; throughput is bounded by connection limits, statement memory caps, and workload-class admission control (concurrency/memory limits) that share capacity with production queries.
What ships with Apache Pinot ⇄ SAP Hana

Connect Apache Pinot and SAP Hana for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Apache Pinot–SAP Hana connection.

Real-time

Two-way sync

Changes in Apache Pinot or SAP Hana instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Apache Pinot or SAP Hana data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Apache Pinot or SAP Hana record.

Observability

Monitoring

Track your Apache Pinot ⇄ SAP Hana sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Apache Pinot and SAP Hana.

How the Apache Pinot and SAP Hana connectors work

Apache Pinot

Integration surface
REST API (SQL queries via the broker; administration via the controller); JDBC client available
Authentication
Deployment-dependent: HTTP basic authentication or token-based auth where enabled
Change detection
Not applicable for reads out (polling by time column); data enters Pinot via streaming ingestion or segment upload, not row-level writes
Capabilities
read · write
Rate limits
No fixed API quotas; query throughput depends on broker and server sizing

SAP Hana

Integration surface
SQL over the SAP HANA client (JDBC/ODBC drivers); OData/REST via XS for app-layer access
Authentication
Dedicated database user credentials over an encrypted TLS connection (password sent hashed); Kerberos, SAML, JWT, and X.509 certificate authentication are also supported. SAP HANA Cloud enforces TLS and IP allowlisting.
Change detection
Polling on a last-modified timestamp column, or AFTER INSERT/UPDATE/DELETE triggers writing to a shadow table; system-versioned temporal tables and SLT/SDI provide trigger- and log-based CDC. No native webhooks.
Capabilities
read · write · CDC
Rate limits
No SaaS-style request quota; throughput is bounded by connection limits, statement memory caps, and workload-class admission control (concurrency/memory limits) that share capacity with production queries.
How it works

How to connect Apache Pinot to SAP Hana — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Apache Pinot and SAP Hana with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Apache Pinot connected
    SAP Hana connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Apache Pinot and SAP Hana objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Apache Pinot ⇄ SAP Hana
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Apache Pinot SAP Hana
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Apache Pinot and SAP Hana integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 471 integrations available for Apache Pinot and SAP Hana.

Popular · 5 of 471
All Apache Pinot integrations All SAP Hana integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own