With 26 +1 votes (11 binding) and no -1 or +0 votes, this passes. Thank you, everyone! It is awesome to see the progress that we've made to get all these features ready.
Ryan On Wed, May 21, 2025 at 10:10 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 >> >
