DatriseAI-first ETL

Apache Spark to Holistics Integration

AI-first ETL from Apache Spark into Holistics. Governed entities, incremental sync, typed landing tables.

How Datrise loads Apache Spark into Holistics

Datrise syncs Apache Spark's jobs, stages, tasks, executors, SQL queries, and application metrics into Holistics as warehouse tables modeled in Holistics. Flexible or custom fields land in flattened columns for the modeling layer, and timestamps such as created, updated, and status changes are typed as date/time dimensions.

Sync is incremental: Datrise uses incremental refresh of the modeled tables, so re-runs update only what changed. Date-partitioned facts for fast aggregates. Holistics models data as code on top of SQL, so Datrise lands stable column names to keep your models from drifting.

Ideal for as-code BI modeling on a warehouse.

Endpoints

Apache Spark: Distributed engine for large-scale data processing.

Holistics: Self-service BI with modeling layers and scheduled report delivery.

How Apache Spark entities map to Holistics

Apache Spark entityHolistics objectNotes
jobsapache_spark_jobsid PK · custom fields → flattened columns for the modeling layer
stagesapache_spark_stagesid PK · linked to apache_spark_jobs
tasksapache_spark_tasksid PK · linked to apache_spark_jobs
executorsapache_spark_executorsid PK · linked to apache_spark_jobs

FAQ

How does Datrise handle Apache Spark's custom fields in Holistics?

Flexible values are stored as flattened columns for the modeling layer, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Holistics types.

How does the Apache Spark to Holistics sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the modeled tables.

Related pipelines

Early access

Connect Apache Spark to Holistics the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.