DatriseAI-first ETL

Docker Hub to Yellowfin Integration

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

How Datrise loads Docker Hub into Yellowfin

Datrise syncs Docker Hub's repositories, images, tags, pull counts, image manifests, and organizations into Yellowfin as warehouse tables Yellowfin builds views on. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date/time dimensions.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts. Yellowfin views reference columns by name, so Datrise lands stable, well-typed columns to keep reports valid.

Ideal for dashboards with automated data storytelling.

Endpoints

Docker Hub: Container image registry and distribution.

Yellowfin: BI suite with dashboards, automated insights, and data storytelling.

How Docker Hub entities map to Yellowfin

Docker Hub entityYellowfin 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 Yellowfin?

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 Yellowfin types.

How does the Docker Hub to Yellowfin sync stay up to date?

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

Related pipelines

Early access

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