Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

[Feature] Support File Index V2 and streaming index writes

Offen
  • Stimmt etwas nicht?
#445 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 3 Tagen

@zjw1111 arbeitet bereits daran.

Seit 19.10.2026.

  • #446 von @zjw1111 — offen

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
25/100
Issue-Typ
Feature
Klarheit
Klar beschrieben
Aktivitätsstatus
Veraltet
Tech-Stack
cpp
Bereich
backend, databases

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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!
Vorherrschende Sprache
C++
Sterne
68
Forks
34
Ø Merge
4 T. 37 Min.
Gemergte PRs (30 T.)
35

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus apache/paimon-cpp

Alle Issues in apache/paimon-cpp

Ähnliche Issues

Weitere Issues zu C++

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.