Parquet File to GoodData Integration
AI-first ETL from Parquet File into GoodData. Governed entities, incremental sync, typed landing tables.
How Datrise loads Parquet File into GoodData
Datrise syncs Parquet File's row groups, columns, schemas, partitions, file batches, and column statistics 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
Parquet File: Columnar Parquet files from lakes and exports.
GoodData: Composable analytics platform with headless BI and embedded dashboards.
How Parquet File entities map to GoodData
| Parquet File entity | GoodData object | Notes |
|---|---|---|
| row groups | parquet_file_row_groups | id PK · custom fields → flattened columns |
| columns | parquet_file_columns | id PK · linked to parquet_file_row_groups |
| schemas | parquet_file_schemas | id PK · linked to parquet_file_row_groups |
| partitions | parquet_file_partitions | id PK · linked to parquet_file_row_groups |
FAQ
How does Datrise handle Parquet File'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 Parquet File to GoodData sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the connected tables.
Related pipelines
More destinations for Parquet File
- Parquet File → Klipfolio
- Parquet File → MicroStrategy
- Parquet File → Spotfire
- Parquet File → Yellowfin
- Parquet File → PostgreSQL
- Parquet File → MySQL
- Parquet File → Microsoft SQL Server
- Parquet File → Oracle Database
- Parquet File → Snowflake
- Parquet File → Google BigQuery
- Parquet File → Amazon Redshift
- Parquet File → Databricks SQL Warehouse
Early access
Connect Parquet File 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.