Re: [DISCUSS] Row lineage required for v3

Okay, it sounds like we have consensus that it's a good idea to make row lineage required in v3 and that it's a good idea to signal to engines when they can write delete-and-insert changes. I think we need a bit more discussion on how to signal to engines, but in the meantime we can move forward wi

Re: [DISCUSS] Multi-arg transforms

1. This makes sense to me, it was the only one requested in the past. It should allow "IN" as well. 2.What's the suggestion here? To allow both source-id and source-ids in V3 but error out if the two don't match? Trying to determine how the validation would look in both cases On Tue, Mar 25, 2025

[DISCUSS] Multi-arg transforms

Hi everyone, I wanted to get your attention to some small changes to the multi-arg transforms that I've bumped into while working on the V3 spec for PyIceberg. 1. Up for debate. The spec does not point out an actual implementation of transforms

Re: [VOTE][Go] Release Apache Iceberg Go v0.2.0 RC1

+1 (binding) Thanks for running this release Matt, and for adding the additional tests! Checked the V1/V2 metadata/manifests/manifest-list, all looks good. Ran tests against the REST catalog and everything seems to work great! Checked the signatures, checksums and licenses. Kind regards, Fokko

Re: [VOTE] Minor simplifications for Geo Spec

Late to the party :) Thanks Szehon +1 (non-binding) On Sun, Mar 23, 2025 at 5:53 PM Szehon Ho wrote: > Thanks all for voting! > > The vote result is: > > +1: 9 (binding: Renjie, Eduard, Fokko, Yufei, Ryan, Daniel, Amogh, > Russell, Szehon), 9 (non-binding: Jia, Gang, Bryan, Huang-Hsiang, Matt,