DatriseAI-first ETL

TiDB to ThoughtSpot Integration

AI-first ETL from TiDB into ThoughtSpot. Governed entities, incremental sync, typed landing tables.

How Datrise loads TiDB into ThoughtSpot

Datrise syncs TiDB's tables, rows, schemas, indexes, regions, and TiCDC change events into ThoughtSpot as warehouse tables ThoughtSpot indexes for search. Flexible or custom fields land in flattened columns for searchable fields, and timestamps such as created, updated, and status changes are typed as date/time columns.

Sync is incremental: Datrise uses incremental refresh of the indexed tables, so re-runs update only what changed. Date-partitioned facts for live-query performance. ThoughtSpot search relies on clear names and relationships, so Datrise lands well-named, joinable tables.

Ideal for natural-language search analytics over a warehouse.

Endpoints

TiDB: MySQL-compatible HTAP database with row and column stores.

ThoughtSpot: Search-driven analytics with AI-assisted insights on warehouse data.

How TiDB entities map to ThoughtSpot

TiDB entityThoughtSpot objectNotes
tablestidb_tablesid PK · custom fields → flattened columns for searchable fields
rowstidb_rowsid PK · linked to tidb_tables
schemastidb_schemasid PK · linked to tidb_tables
indexestidb_indexesid PK · linked to tidb_tables

FAQ

How does Datrise handle TiDB's custom fields in ThoughtSpot?

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

How does the TiDB to ThoughtSpot sync stay up to date?

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

Related pipelines

Early access

Connect TiDB to ThoughtSpot 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.