Repository navigation
V3 Tracking issue #1818
Description
Tracks the progress of the V3 implementation
- New DataTypes
- UnknownType: Added in feat: Add unknown type #1681
- Timestamp(Tz)NanoType: Introduced in V3: Introduce
timestamp_nsandtimestamptz_ns#1632 - VariantType: Add
VariantType#1819 - Geometry/Geography: Add
GeometryType/GeographyType#1820
- Default value:
- Multi-arg transforms
- Reading of the metadata has been added in Add V3 read support #1554
- Supporting multi-arg transforms still needs to happen
- Row-level lineage
- Deletion vectors
- Read support is being added in Deletion Vectors read support #1516
- Write support
Activity
[-]V3 Progress[/-][+]V3 Tracking issue[/+]sungwy commentedon Mar 21, 2025
I'd love to get my hands on working with some more new types (when the dependencies are resolved).
Could you assign me to either the VariantType or GeoTypes? (or both? haha) :)
Fokko commentedon Mar 24, 2025
Hey @sungwy it is first come first serve! :D Please check out the issues of the types itself. I think there are some dependencies, but curious to learn what you think.
smaheshwar-pltr commentedon May 6, 2025
Happy to see an issue tracking this 🚀 !
The V3 spec changes for encryption have merged in apache/iceberg#12162. There's an open PR (edit: now merged) for the resultant changes to table metadata on the Java side here - apache/iceberg#12927.
@Fokko, can we add encryption to the list here, so we're tracking it somewhere for PyIceberg? (Update: I put up #1972 for metadata read change tracking)
yingjianwu98 commentedon May 31, 2025
@Fokko
I see that read for equality deletes are not implemented yet and write for both positional/equality deletes are also not implemented.
I am aware that the community deprecates position deletes in v3 and might deprecate equality deletes as well in the future so want to ask what is the vision for pyiceberg on these topics, thanks!
kevinjqliu commentedon Jun 14, 2025
@stevie9868
DV read is implemented in #1516. I dont think anyone has started on write support
Even with the deprecation, I think it would be nice to support reading equality deletes for feature completeness.
Writing positional deletes would be nice too.
Writing equality deletes is nice but we'd like to discourage writing equality deletes due to deprecation
rambleraptor commentedon Jun 30, 2025
@stevie9868 are you still planning on taking on the deletion vector work? I'm happy to contribute some cycles if you don't have any
yingjianwu98 commentedon Jul 1, 2025
@rambleraptor
yeah, I am planning to work on it soon.
There is an ongoing work to build the DeleteFileIndex, which the DV work might depend on.
aschreiber1 commentedon Nov 14, 2025
Can the current version of pyiceberg read an v3 table correctly?
glesperance commentedon Dec 6, 2025
This is very exciting.
I see the deletion vector write support is still pending. Is this something under way or is it something the community could help with?
cc @yingjianwu98 @rambleraptor
geruh commentedon Dec 10, 2025
@rambleraptor opened write support pr here: #2822
jhamman commentedon Aug 28, 2026
Hi folks -- It looks like the Geometry/Geography box above can be ticked now that #2859 went in.
Curious if there is an update on the outlook for v3 support in iceberg-python?