[Feature] Support File Index V2 and streaming index writes
维护者通常 3 天内回复
评估
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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-versionvalues1and2, keeping V1 as the default. - Add
FileIndexWriter::WriteTo()so plugins can write payloads directly to a caller-owned stream. Keep a default implementation based onSerializedBytes()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!
- 主要语言
- C++
- 星标
- 68
- 派生
- 34
- 平均合并
- 4 天 37 分钟
- 30 天内合并 PR
- 35
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
apache/paimon-cpp 的其他 Issue
-
难度 5/5 一周以上 新手友好度 8/100
apache/paimon-cpp#435 · 2 条评论 ·
维护者通常 3 天内回复
-
enhancement
难度 5/5 一周以上 新手友好度 35/100
apache/paimon-cpp#410 ·
维护者通常 3 天内回复
-
enhancement
难度 5/5 一周以上 新手友好度 25/100
apache/paimon-cpp#409 ·
维护者通常 3 天内回复
-
enhancement
难度 5/5 一周以上 新手友好度 35/100
apache/paimon-cpp#408 ·
维护者通常 3 天内回复
-
enhancement
难度 5/5 一周以上 新手友好度 35/100
apache/paimon-cpp#407 ·
维护者通常 3 天内回复
查看 apache/paimon-cpp 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
category:port-update
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 2 天内回复
-
(S1 - Need confirmation)
难度 2/5 1-3 小时 新手友好度 65/100
CleverRaven/Cataclysm-DDA#89194 ·
维护者通常 1 天内回复
-
reproduced
难度 1/5 1 小时以内 新手友好度 67/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复