I also noticed that some of the tables shared by v2 and v3 didn't mention v3. I've updated the headers to include v3 for clarity. Please let me know if this change requires a separate vote thread: https://github.com/apache/iceberg/pull/13181
- Ajantha On Wed, May 28, 2025 at 10:27 PM Ajantha Bhat <ajanthab...@gmail.com> wrote: > Since the voting is passed, I went ahead and created the PR to update the > spec that v3 is complete. > https://github.com/apache/iceberg/pull/13175 > > This has came up in one of the recent discussions in > https://github.com/apache/iceberg/pull/13123#discussion_r2105451519 > > - Ajantha > > On Fri, May 23, 2025 at 7:37 AM John Zhuge <jzh...@apache.org> wrote: > >> +1 (non-binding) >> >> On Wed, May 21, 2025 at 10:09 AM Brian Hulette <bhule...@apache.org> >> wrote: >> >>> +1 (non-binding) >>> >>> On Wed, May 21, 2025 at 12:56 AM Jean-Baptiste Onofré <j...@nanthrax.net> >>> wrote: >>> >>>> +1 (non binding) >>>> >>>> Regards >>>> JB >>>> >>>> On Mon, May 19, 2025 at 11:20 PM Ryan Blue <rdb...@gmail.com> wrote: >>>> > >>>> > Hi everyone, >>>> > >>>> > With the follow-ups from the earlier discussion thread wrapped up, >>>> I’d like to raise a vote to adopt the v3 spec changes. >>>> > >>>> > What is included? >>>> > >>>> > Default values for columns and fields >>>> > New types: variant, geospatial, timestamp(9), and unknown >>>> > Row lineage and change tracking using synthetic row IDs and row-level >>>> last modified sequence number >>>> > Improved position deletes using binary deletion vectors that are >>>> synchronously maintained >>>> > Table encryption key tracking >>>> > Table metadata support for future multi-argument transforms >>>> > >>>> > What does adopting these changes mean? >>>> > >>>> > Adopting the changes signals that we (the community) intend to >>>> support the current set of changes and will maintain forward-compatibility >>>> for v3 tables that implement the v3 spec. After adopting the changes, >>>> future breaking changes would go into v4. >>>> > >>>> > As with v2 adoption, this is needed to build support in downstream >>>> projects and other implementations. Adoption doesn’t change the default >>>> table version, it signals that there will be no further break changes in v3 >>>> and that we are confident in supporting the v3 features. >>>> > >>>> > Huge thanks to everyone that has worked to get to this point with the >>>> v3 changes! >>>> > >>>> > Please vote in the next 72 hours: >>>> > >>>> > [ ] +1 Adopt the v3 changes to the table spec >>>> > [ ] +0 >>>> > [ ] -1 Wait to close v3 changes because . . . >>>> > >>>> > Ryan >>>> >>> >> >> -- >> John Zhuge >> >
