DatriseAI-first ETL

Teradata to Apache Superset Integration

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

How Datrise loads Teradata into Apache Superset

Datrise syncs Teradata's tables, rows, schemas, indexes, primary indexes, and query history into Apache Superset as governed SQL tables Superset queries directly. Flexible or custom fields land in flattened columns for the explore UI, and timestamps such as created, updated, and status changes are typed as temporal columns for time-series charts.

Sync is incremental: Datrise uses incremental refresh of the queried tables, so re-runs update only what changed. Date-partitioned tables to keep dashboards responsive. Superset charts run live SQL, so Datrise lands query-friendly, indexed tables rather than wide raw payloads.

Ideal for open-source dashboards over your own database.

Endpoints

Teradata: Teradata analytical database for enterprise workloads.

Apache Superset: Open-source BI for SQL exploration, charts, and dashboard publishing.

How Teradata entities map to Apache Superset

Teradata entityApache Superset objectNotes
tablesteradata_d_tablesid PK · custom fields → flattened columns for the explore UI
rowsteradata_d_rowsid PK · linked to teradata_d_tables
schemasteradata_d_schemasid PK · linked to teradata_d_tables
indexesteradata_d_indexesid PK · linked to teradata_d_tables

FAQ

How does Datrise handle Teradata's custom fields in Apache Superset?

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

How does the Teradata to Apache Superset sync stay up to date?

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

Related pipelines

Early access

Connect Teradata to Apache Superset 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.