Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

[Feature] Support File Index V2 and streaming index writes

Fermée
#445 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 3 jours

Une pull request liée a déjà été fusionnée.

  • #446 par @zjw1111 — fusionnée

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
25/100
Type d'issue
Fonctionnalité
Clarté
Clairement spécifiée
Activité
À l'abandon
Stack technique
cpp
Domaine
backend, databases

Piste de recherche

Start by reading the existing File Index container and write path, then compare the V2 layout with the Java reference PR #10101 and the related work in #173. The issue names no source files or tests, so locate the container, writer, plugin interfaces, and spillable output stream before estimating the changes. Done means V1 compatibility remains, V2 reads and writes Java-compatible bytes, and the listed payload, empty-index, and spill-threshold cases are covered; an open linked PR #446 is already working on it.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

enhancement
Search before asking
  • I searched in the issues and found no existing issue specifically tracking File Index V2.
Motivation

The V1 File Index container uses 32-bit payload offsets and lengths. The existing write path also materializes serialized index payloads and the complete container in memory before deciding whether to embed the index or write an external file. These limitations make it difficult to support large index artifacts, especially vector indexes.

Java Paimon introduced a V2 container with 64-bit payload ranges and a streaming write interface. Paimon C++ should support the same format while retaining V1 compatibility.

Solution
  • Add V2 container reading and writing, with int64 payload offsets and lengths and a footer/trailer layout aligned with Java Paimon.
  • Support file-index.format-version values 1 and 2, keeping V1 as the default.
  • Add FileIndexWriter::WriteTo() so plugins can write payloads directly to a caller-owned stream. Keep a default implementation based on SerializedBytes() and implement direct streaming output for Lumina.
  • Widen plugin reader offsets and lengths to int64, with plugin-specific size limits checked inside the affected plugins.
  • Integrate a spillable output stream into the data-file index write path, embedding small containers and spilling larger ones to external files without buffering the complete V2 container.
  • Add focused coverage for V1 compatibility, Java-generated V2 golden bytes, large payload ranges, empty indexes, and spill thresholds.

The V2 container's 64-bit ranges do not imply that every index plugin supports payloads larger than 2 GiB; individual plugin serialization formats may retain their own limits.

Anything else?

Java reference: https://github.com/apache/paimon/pull/10101

Related to File Index writing in #173.

Are you willing to submit a PR?
  • I'm willing to submit a PR!
Langage dominant
C++
Étoiles
70
Forks
36
Merge moyen
3 j 9 h
PR mergées (30 j)
42

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de apache/paimon-cpp

Toutes les issues de apache/paimon-cpp

Issues similaires

Plus d'issues C++

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.