Two-way sync
Changes in Apache Druid or Odoo instantly reflect in both systems. No stale data, no manual imports.
Keep Apache Druid and Odoo in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.
ERP data is some of the most asked-for data in the warehouse and some of the hardest to get: the record types are many, the APIs are strict, and extract jobs are brittle. Whether Odoo carries financials, operations, workforce data, or all three, the analysis belongs in Apache Druid next to everything else the company measures.
Stacksync syncs Employees (hr.employee), Projects and Tasks (project.project / project.task), Contacts (res.partner), Sales Orders (sale.order) from Odoo into tables in Apache Druid continuously, managing API limits and schema drift along the way. The connection is bi-directional, so values computed in Apache Druid can be written back to fields in Odoo where that is useful.
Combine Odoo's records with data synced from other systems in Apache Druid for consolidated views no single system can produce.
Classifications or reference values computed in Apache Druid sync back onto the corresponding records in Odoo.
Financial records land in Apache Druid as they change, so period-end reporting queries current numbers rather than last night's extract.
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 | Odoo objects | How this pairing syncs | |
|---|---|---|---|
| Datasources The table-like unit of storage and querying, the main target of reads and ingestion. | Products (product.template / product.product) Catalog and variant data distributed to storefronts and quoting tools. | Datasources is specific to Apache Druid and Products (product.template / product.product) to Odoo — each maps to any object or custom field on the other side. | |
| Segments Time-partitioned immutable files that hold datasource data; ingestion produces them. | CRM Leads (crm.lead) Leads and opportunities synced with marketing and enrichment systems. | Segments is specific to Apache Druid and CRM Leads (crm.lead) to Odoo — 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. | Purchase Orders (purchase.order) Procurement documents shared with supplier-facing systems. | Dimensions is specific to Apache Druid and Purchase Orders (purchase.order) to Odoo — each maps to any object or custom field on the other side. | |
| Metrics Numeric columns, often pre-aggregated at ingestion via rollup. | Inventory Transfers (stock.picking) Delivery and receipt operations synced for fulfillment visibility. | Metrics is specific to Apache Druid and Inventory Transfers (stock.picking) to Odoo — each maps to any object or custom field on the other side. | |
| Ingestion Supervisors Long-running specs that pull from streams like Kafka; the write path into Druid. | Employees (hr.employee) HR records read for directory and provisioning syncs. | Ingestion Supervisors is specific to Apache Druid and Employees (hr.employee) to Odoo — each maps to any object or custom field on the other side. | |
| Lookups Key-value mappings joined at query time, refreshable from external systems. | Projects and Tasks (project.project / project.task) Work items synced with external project tools. | Lookups is specific to Apache Druid and Projects and Tasks (project.project / project.task) to Odoo — each maps to any object or custom field on the other side. |
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.
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.
DeliveryEach detected change is written to Odoo through its API, with automatic retries and rate-limit backoff.
DetectionOdoo notifies Stacksync of record changes through webhook events. Polling on the write_date timestamp every record carries.
DeliveryEach detected change is applied to Apache Druid as a row-level write, with types converted between the two schemas.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Apache Druid–Odoo connection.
Changes in Apache Druid or Odoo instantly reflect in both systems. No stale data, no manual imports.
Trigger automated workflows whenever Apache Druid or Odoo data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.
Handle millions of events per minute without losing a single Apache Druid or Odoo record.
Track your Apache Druid ⇄ Odoo sync health, view errors, and replay failed events in one click.
Transform legacy EDI complexity into simple database interactions between Apache Druid and Odoo.
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.
Authenticate Apache Druid and Odoo with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Pick the Apache Druid and Odoo 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.
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Yes. Stacksync provides a managed, real-time two-way integration between Apache Druid and Odoo: authenticate both systems, choose the objects to sync (such as Apache Druid's Datasources and Segments), map fields visually, and changes propagate both ways in milliseconds — no code required.
Change detection on Apache Druid: Not applicable for reads out (polling by time interval); data enters Druid through streaming or batch ingestion rather than row updates. On Odoo: Polling on the write_date timestamp every record carries; recent versions can also send outbound webhooks from automation rules. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
On the Apache Druid side: Metrics, Ingestion Supervisors, Lookups, Tasks, plus custom fields where Apache Druid exposes them. On the Odoo side: Employees (hr.employee), Projects and Tasks (project.project / project.task), Contacts (res.partner), Sales Orders (sale.order). Stacksync auto-detects both schemas and converts types between the two systems.
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
Common patterns for Apache Druid and Odoo: Group reporting across systems; Write-back where Odoo exposes writable fields; Where Odoo holds the books: finance reporting from live data. Combine Odoo's records with data synced from other systems in Apache Druid for consolidated views no single system can produce.
Apache Druid: 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. Odoo: XML-RPC and JSON-RPC external API exposing the full ORM (search_read, create, write, unlink). Authentication: Database user credentials or per-user API keys. Stacksync manages authentication, retries, and rate limits on both sides.
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.
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Securely connects to your systems with:
Every pair below is a real-time, two-way sync. Search all 454 integrations available for Apache Druid and Odoo.