Blob v2 raw file reader fails on files with anonymous descriptor child IDs

Abierto
#10,944 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
47/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
rust
Área
backend, data

Línea de trabajo

Start by comparing the raw-file reader path in rust/lance-file/src/reader.rs with normalize_blob_footer_schema in rust/lance-file/src/concat.rs, which the issue says is only used by concatenation. Trace how Schema::try_from(&Fields) handles Blob v2 descriptor children with parent_id == -1. Add reader-side normalization for existing files, then cover the C and native writers and readers, both projection modes, NULL and empty rows, an ordinary-column control, and a file from the current writer.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

A v2.2 file with one physical Blob v2 column (3 rows) fails through the ordinary raw-file reader. The failure reproduces with files written by both the C and native Rust writers, and with both the public C FileReader and the direct native Rust FileReader.

Pinned: Lance v14.0.2 (40f15ed1b71b66950961b175829fdf17a763f108).

Symptoms
  • Whole-schema projection: the footer reconstructs six top-level fields, giving [0,5,5,5,5,5]; the reader returns The projection specified the column index 5 but there are only 1 columns in the file (rust/lance-file/src/reader.rs:1174).
  • Explicit columns=["blob"]: projection [0] passes, but Blob is exposed as Struct([]); consuming the stream returns Structural validity has 3 entries for an array with 0 values (rust/lance-encoding/src/encodings/logical/primitive/field.rs:874).
  • An ordinary id column alongside Blob fails analogously with index 6 for two physical columns.
Root cause

Field::unloaded_mut copies the BLOB_V2_DESC_LANCE_FIELD children; their ids and parent_id are -1. The structural writer persists them, and read-side Schema::try_from(&Fields) treats every parent_id == -1 field as a root, so the five descriptor children become orphan top-level fields and the Blob parent loses its children.

normalize_blob_footer_schema handles this shape but is only used by concatenation (rust/lance-file/src/concat.rs:270). Dataset scanning has separate Blob projection handling, so dataset reads pass while the raw-file reader fails.

Requested fix

A reader-side normalization for already-written files. A writer-side ID fix alone cannot repair existing files.

Tests should cover: C and native writers × C and native readers; default and explicit projections; NULL/empty rows; an ordinary-column control; and a pre-existing file produced by the current writer.

Notes

As of lance-format/lance main 58e62bd546081357e2b8966e12ef9bb5c5debbb1 (2026-11-11), the reader path is unchanged and no official fix was found in the checked code.

Reproducer/evidence: lance-format/lance-c#167. Related: lance-format/lance-c#99, lance-format/lance-c#114, lance-format/lance-c#115, lance-format/lance-c#162.

Lenguaje dominante
Rust
Estrellas
7.3k
Forks
929
Merge medio
2 d 22 h
PR fusionados (30 d)
572

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

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 lance-format/lance

Todos los issues de lance-format/lance

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.