Firebolt to GoodData Integration
AI-first ETL from Firebolt into GoodData. Governed entities, incremental sync, typed landing tables.
How Datrise loads Firebolt into GoodData
Datrise syncs Firebolt's databases, tables, aggregating indexes, query jobs, table schemas, and partitions into GoodData as warehouse tables GoodData maps into its logical data model. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date dimensions.
Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts. GoodData's LDM maps datasets by keys, so Datrise lands stable primary and foreign id columns to keep the model valid.
Ideal for embedded, multi-tenant analytics.
Endpoints
Firebolt: Cloud data warehouse tuned for fast analytics.
GoodData: Composable analytics platform with headless BI and embedded dashboards.
How Firebolt entities map to GoodData
| Firebolt entity | GoodData object | Notes |
|---|---|---|
| databases | firebolt_databases | id PK · custom fields → flattened columns |
| tables | firebolt_tables | id PK · linked to firebolt_databases |
| aggregating indexes | firebolt_aggregating_indexes | id PK · linked to firebolt_databases |
| query jobs | firebolt_query_jobs | id PK · linked to firebolt_databases |
FAQ
How does Datrise handle Firebolt's custom fields in GoodData?
Flexible values are stored as flattened columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native GoodData types.
How does the Firebolt to GoodData sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the connected tables.
Related pipelines
More destinations for Firebolt
Early access
Connect Firebolt to GoodData 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.