Skip to content
Data warehouse ⇄ Analytics

Apache Druid to Tableau integration — real-time data sync

Keep Apache Druid and Tableau 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 Druid and Tableau

Flow Tableau data into Apache Druid in real time — no exports, no schedulers, no custom scripts.

Tableau is a read-only source: Stacksync reads its data in real time and delivers it into Apache Druid, so Apache Druid always reflects the current state of Tableau — without exports, scripts, or schedulers.

Tableau is where teams explore, visualize, and report; Apache Druid is the store of record that holds the raw tables and full history behind those views. The two overlap wherever the same events, users, and metrics matter to both, and when the bridge between them is a nightly export or a hand-built extract, dashboards lag the warehouse and analysts spend the morning arguing over whose number is right.

Common use cases

  • 01 Read site Users and their site roles for periodic access reviews and to reconcile Tableau accounts against an HR or IdP source of record.
  • 02 Read Databases, Tables, and Fields from the Metadata API to populate a data catalog with Tableau lineage and column definitions.
  • 03 Sync Druid query results into a warehouse to combine real-time aggregates with historical models.
  • 04 Keep lookup tables in Druid refreshed from a CRM or database so query-time joins use current reference data.

Common sync patterns

Corrections propagate instead of reloading

When a record is fixed or backfilled on one side, the change reaches the other without a full reload, keeping history consistent across both.

One number both sides agree on

Metrics and aggregates stay aligned between the two systems, so a figure shown in Tableau matches the Apache Druid table it was built from instead of drifting between refreshes.

Where Apache Druid holds the source tables: live data in the reporting layer

Records maintained in Apache Druid flow into Tableau as they change, so dashboards and reports read current rows rather than an overnight extract.

What you can sync between Apache Druid and Tableau

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 Druid objects Tableau objects How this pairing syncs
Lookups Key-value mappings joined at query time, refreshable from external systems. Fields and Columns Columns and calculated fields with their descriptions, exposed by the Metadata API; read to populate a data catalog with governed definitions. Lookups is specific to Apache Druid and Fields and Columns to Tableau — each maps to any object or custom field on the other side.
Tasks Batch ingestion and compaction jobs monitored during data loads. Published Data Sources Published data sources (.tdsx); their underlying rows are read via the VizQL Data Service, and refresh state is tracked through content webhooks. Tasks is specific to Apache Druid and Published Data Sources to Tableau — each maps to any object or custom field on the other side.
Datasources The table-like unit of storage and querying, the main target of reads and ingestion. Workbooks Workbook content and metadata read via the REST and Metadata APIs; create, update, and delete events fire webhooks for change detection. Datasources is specific to Apache Druid and Workbooks to Tableau — each maps to any object or custom field on the other side.
Segments Time-partitioned immutable files that hold datasource data; ingestion produces them. Views Worksheets and dashboards inside workbooks; their data and crosstab export as CSV via the REST query-view-data endpoint. Segments is specific to Apache Druid and Views to Tableau — each maps to any object or custom field on the other side.
Dimensions String and categorical columns used for filtering and grouping in synced queries. Projects Folders that organize content and set permissions; listed via REST to mirror the site's content hierarchy into a catalog. Dimensions is specific to Apache Druid and Projects to Tableau — each maps to any object or custom field on the other side.
Metrics Numeric columns, often pre-aggregated at ingestion via rollup. Users Site users with site roles and group membership; read via REST for access reviews and to reconcile identities against an HR or IdP source. Metrics is specific to Apache Druid and Users to Tableau — each maps to any object or custom field on the other side.

How changes propagate between Apache Druid and Tableau

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 Druid Tableau Interval-based propagation

DetectionStacksync polls Apache Druid for changes on an incremental schedule, reading only records changed since the previous pass. Data enters Druid through streaming or batch ingestion rather than row updates.

DeliveryTableau does not accept inbound record writes, so this direction carries requests rather than records: Tableau's output flows back as field updates on the originating Apache Druid records.

Tableau Apache Druid Sub-second propagation

DetectionTableau notifies Stacksync of record changes through webhook events. Webhooks fire on workbook and data source create/update/delete and extract refresh events.

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

Rate-limit considerations

  • Apache Druid: No fixed API quotas; query concurrency is bounded by broker and historical node capacity.
  • Tableau: Tableau Cloud enforces per-site REST rate limits and returns HTTP 429; a PAT allows only one concurrent session and expires after 15 consecutive days of non-use.
What ships with Apache Druid ⇄ Tableau

Connect Apache Druid and Tableau for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Apache Druid–Tableau connection.

Real-time

Real-time sync

Changes in Apache Druid or Tableau instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Apache Druid or Tableau 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 Druid or Tableau record.

Observability

Monitoring

Track your Apache Druid ⇄ Tableau sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Apache Druid and Tableau.

How the Apache Druid and Tableau connectors work

Apache Druid

Integration surface
REST API (SQL over HTTP and native JSON queries); JDBC via Avatica
Authentication
Deployment-dependent: basic authentication or an authenticator extension; often fronted by a proxy
Change detection
Not applicable for reads out (polling by time interval); data enters Druid through streaming or batch ingestion rather than row updates
Capabilities
read · write
Rate limits
No fixed API quotas; query concurrency is bounded by broker and historical node capacity

Tableau

Integration surface
REST API, Metadata API (GraphQL), and VizQL Data Service
Authentication
Sign-in via Personal Access Token (PAT) or username/password returns a credentials token sent as the X-Tableau-Auth header; Connected Apps issue JWTs for OAuth-style access. One active session per PAT.
Change detection
Webhooks fire on workbook and data source create/update/delete and extract refresh events; otherwise content and metadata are polled via REST list endpoints (updatedAt) and the Metadata API.
Capabilities
read · webhooks
Rate limits
Tableau Cloud enforces per-site REST rate limits and returns HTTP 429; a PAT allows only one concurrent session and expires after 15 consecutive days of non-use.
How it works

How to connect Apache Druid to Tableau — 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 Druid and Tableau 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 Druid connected
    Tableau connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Apache Druid and Tableau 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 Druid ⇄ Tableau
    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 Druid Tableau
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Apache Druid and Tableau 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
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 372 integrations available for Apache Druid and Tableau.

Popular · 7 of 372
All Apache Druid integrations All Tableau 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