Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

datalake_fdw: Iceberg name mapping for data files without field ids

Abierto
#1,989 0 comentarios 0 reacciones 1 asignado Ver en GitHub

@MisterRaindrop ya está trabajando en esto.

Desde el 13/9/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

datalake
Summary

Since #1951 the Parquet reader in contrib/datalake_fdw matches a table's columns to a file's by Iceberg field id (PARQUET:field_id in the Parquet schema). A file whose columns carry no field id can never be matched: every projected column reads as NULL. That is correct per spec for a file the table never wrote, and wrong for the one case the spec covers: tables created over existing Parquet data (add_files, migrated Hive tables), whose files predate the ids.

What the spec says

Iceberg resolves such files through the table property schema.name-mapping.default: a JSON mapping from field ids to the column names to look for in the file, including nested names and multiple names per id (for renamed columns). A reader applies it only to columns that have no field id.

What has to happen
  • The metadata engine has to surface the property to the access method.
  • ProjectionSet (format/format.h) needs a way to hand the reader a name mapping alongside the field ids -- a second array of names per id, or a pointer to a parsed mapping.
  • parquet_read.cpp's parquet_project() matches by id first and falls back to the mapping for id-less columns. Nothing changes in the decoder.
  • A file with neither ids nor a mapping match stays NULL, as now.

Deferred from #1951 on purpose: the framework there is settled, and the property needs the metadata engine, which is a later PR.

Lenguaje dominante
C
Estrellas
1.4k
Forks
248
Merge medio
4 d 10 h
PR fusionados (30 d)
40

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de apache/cloudberry

Todos los issues de apache/cloudberry

Issues similares

Más issues de C

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.