DatriseAI-first ETL

Docker Hub to GoodData Integration

AI-first ETL from Docker Hub into GoodData. Governed entities, incremental sync, typed landing tables.

How Datrise loads Docker Hub into GoodData

Datrise syncs Docker Hub's repositories, images, tags, pull counts, image manifests, and organizations 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

Docker Hub: Container image registry and distribution.

GoodData: Composable analytics platform with headless BI and embedded dashboards.

How Docker Hub entities map to GoodData

Docker Hub entityGoodData objectNotes
repositoriesdockerhub_repositoriesid PK · custom fields → flattened columns
imagesdockerhub_imagesid PK · linked to dockerhub_repositories
tagsdockerhub_tagsid PK · linked to dockerhub_repositories
pull countsdockerhub_pull_countsid PK · linked to dockerhub_repositories

FAQ

How does Datrise handle Docker Hub'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 Docker Hub to GoodData sync stay up to date?

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

Related pipelines

Early access

Connect Docker Hub 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.