Repository navigation
Track Iceberg v3 Feature Support (Roadmap for 0.4.0) #637
Description
Activity
- added a sub-issue
on May 5, 2026 - changed the title
[-]Track Iceberg v3 Feature Support (Target: 0.3.0)[/-][+]Track Iceberg v3 Feature Support (Target: 0.4.0)[/+]on May 5, 2026 @zhjwpku Meanwhile, it might be valuable to create a milestone 0.4.0 to track all issues?
@zhjwpku Meanwhile, it might be valuable to create a milestone 0.4.0 to track all issues?
Good suggestion. We haven't used milestones for previous releases, but I think we should start doing that for future releases. Let me try that.
@zhjwpku Meanwhile, it might be valuable to create a milestone 0.4.0 to track all issues?
Good suggestion. We haven't used milestones for previous releases, but I think we should start doing that for future releases. Let me try that.
Oh, I don't have permission to create milestones. Let's wait for @wgtmac to handle this. I'm not sure if we should do this after the 0.3.0 release.
I think we don't need to support
5. Table-Level Encryption Metadataand6. Puffin-Based Statisticsat the moment.I think we don't need to support
5. Table-Level Encryption Metadataand6. Puffin-Based Statisticsat the moment.Added a comment noting that this is not planned for 0.4.0.
- pinned this issue
on May 22, 2026 I've moved the unfinished items from Roadmap for 0.3.0 (#523) into this issue. Feel free to ping me if I missed anything.
I've also linked the iceberg-go V3 tracking issue [1] here so we can keep track of any V3-related work we might otherwise miss.
- changed the title
[-]Track Iceberg v3 Feature Support (Target: 0.4.0)[/-][+]Track Iceberg v3 Feature Support (Roadmap for 0.4.0)[/+]on Jun 6, 2026 33 remaining items
@zhjwpku @wgtmac I've labeled all open PRs planned here with 0.4.0 milestone. Let's prioritize reviewing them and getting them in.
Reacted by Junwang Zhao, Gang Wu and slfan1989- added a commit that references this issue
on Jul 29, 2026 - added a commit that references this issue
on Sep 8, 2026 - added 2 commits that reference this issue
on Sep 17, 2026 - added a commit that references this issue
on Sep 19, 2026 Remaining items not landing in 0.4.0 (variant, applying column defaults, RewriteManifests, CherryPickOperation, plus the unplanned encryption metadata and Puffin statistics work) are now tracked in #959 for the 0.5.0 milestone.
- added a commit that references this issue
on Oct 9, 2026 #988 is created for table encryption
Reacted by Manu Zhang
We already have partial support for Iceberg v3 in the codebase (e.g., Row Lineage and partition statistics). However, a number of key v3 features are still missing.
This issue serves as a parent tracking issue for the remaining v3 work we plan to (partially) include in the 0.3.0 release.
If you are interested in working on any of the items below, please open a dedicated sub-issue and link it back to this one.
V3 related
1. Schema-Level Support for New v3 Types
Add support for all newly introduced v3 types at the schema level, including:
timestamp_ns,timestamptz_ns@zhjwpkuunknown@manuzhangvariant@zhjwpku rely on arrow, defered to 0.5.0geometry,geography@wgtmac2. Column Default Values (Schema Evolution)
Enable schema evolution with default values:
initial-defaultandwrite-default@huan233usc3. Multi-Argument Transforms (Not planned, as they are not supported by the Java implementation)4. Binary Deletion Vectors
Add support for deletion vectors (DV):
5. Table-Level Encryption Metadata (Not planned for 0.4.0) @shangxinli
Support encryption-related metadata defined in v3:
6. Puffin-Based Statistics (Not planned for 0.4.0)
Support table and partition statistics stored in Puffin files:
Table update and maintenance: #364
Miscellaneous
If anything is missing or you have suggestions, feel free to comment or open additional sub-issues.