[RESULT] [VOTE] Adopt the v2 spec changes

With 10 +1 votes and no +0 or -1 votes, this passes. Thanks, everyone for looking into the format changes and taking the time to vote! And thanks to everyone that worked on getting v2 implemented, tested, and documented! I'll put up some PRs to reflect this change in the spec. Ryan On Sun, Aug

Re: [VOTE] Adopt the v2 spec changes

+1 (binding) Anton > > On Aug 1, 2021, at 2:40 PM, Carl Steinbach wrote: > >  > +1 (binding) > >> On Wed, Jul 28, 2021 at 6:43 PM Daniel Weeks wrote: >> +1 >> >>> On Wed, Jul 28, 2021, 1:36 PM Kyle Bendickson >>> wrote: >>> +1 (non-binding) >>>  >>> >>> Kyle Bendickson >>> Software Eng

Re: [VOTE] Adopt the v2 spec changes

+1 (binding) On Wed, Jul 28, 2021 at 6:43 PM Daniel Weeks wrote: > +1 > > On Wed, Jul 28, 2021, 1:36 PM Kyle Bendickson > wrote: > >> +1 (non-binding) >> >>  >> >> *Kyle Bendickson* >> Software Engineer >> Apple >> ACS Data >> One Apple Park Way, >> Cupertino, CA 95014, USA >> kbendick...@appl

Re: [VOTE] Adopt the v2 spec changes

+1 On Wed, Jul 28, 2021, 1:36 PM Kyle Bendickson wrote: > +1 (non-binding) > >  > > *Kyle Bendickson* > Software Engineer > Apple > ACS Data > One Apple Park Way, > Cupertino, CA 95014, USA > kbendick...@apple.com > > This email and any attachments may be privileged and may contain > confidenti

Re: [VOTE] Adopt the v2 spec changes

+1 (non-binding)  Kyle Bendickson Software Engineer Apple ACS Data One Apple Park Way, Cupertino, CA 95014, USA kbendick...@apple.com This email and any attachments may be privileged and may contain confidential information intended only for the recipient(s) named above. Any other distribution

Re: [VOTE] Adopt the v2 spec changes

FYI, regarding the syntax to allow experimenting with the v2 format easily, I put up a PR: https://github.com/apache/iceberg/pull/2887 -Jack On Wed, Jul 28, 2021 at 12:23 PM Yan Yan wrote: > +1 (non-binding) > > On Wed, Jul 28, 2021 at 10:52 AM Yufei Gu wrote: > >> +1 (non-binding) >> Best, >>

Re: [VOTE] Adopt the v2 spec changes

+1 (non-binding) On Wed, Jul 28, 2021 at 10:52 AM Yufei Gu wrote: > +1 (non-binding) > Best, > > Yufei > > `This is not a contribution` > > > On Wed, Jul 28, 2021 at 8:34 AM Ryan Murray wrote: > >> +1 (non-binding) >> >> On Wed, Jul 28, 2021 at 5:14 PM Russell Spitzer < >> russell.spit...@gmail

Re: [VOTE] Adopt the v2 spec changes

+1 (non-binding) Best, Yufei `This is not a contribution` On Wed, Jul 28, 2021 at 8:34 AM Ryan Murray wrote: > +1 (non-binding) > > On Wed, Jul 28, 2021 at 5:14 PM Russell Spitzer > wrote: > >> +1 (non-binding) >> >> On Jul 28, 2021, at 10:11 AM, Ryan Blue wrote: >> >> +1 >> >> On Tue, Jul

Re: [VOTE] Adopt the v2 spec changes

+1 (non-binding) On Wed, Jul 28, 2021 at 5:14 PM Russell Spitzer wrote: > +1 (non-binding) > > On Jul 28, 2021, at 10:11 AM, Ryan Blue wrote: > > +1 > > On Tue, Jul 27, 2021 at 9:58 AM Ryan Blue wrote: > >> I’d like to propose that we adopt the pending v2 spec changes as the >> supported v2 sp

Re: [VOTE] Adopt the v2 spec changes

+1 (non-binding) > On Jul 28, 2021, at 10:11 AM, Ryan Blue wrote: > > +1 > > On Tue, Jul 27, 2021 at 9:58 AM Ryan Blue > wrote: > I’d like to propose that we adopt the pending v2 spec changes as the > supported v2 spec. The full list of changes is documented in the v2

Re: [VOTE] Adopt the v2 spec changes

+1 On Tue, Jul 27, 2021 at 9:58 AM Ryan Blue wrote: > I’d like to propose that we adopt the pending v2 spec changes as the > supported v2 spec. The full list of changes is documented in the v2 > summary section of the spec . > > The major breaking chan

Re: [VOTE] Adopt the v2 spec changes

Adopting the v2 spec and making support guarantees will mean that we can add table properties to create v2 tables. The reason why it is hard to upgrade to v2 is that we haven't adopted it or made compatibility guarantees, so we don't want people using it in production. On Tue, Jul 27, 2021 at 11:5

Re: [VOTE] Adopt the v2 spec changes

> adopt the pending v2 spec changes as the supported v2 spec I assume this vote wants to reach the consistency between the community members that we won't introduce any breaking changes in v2 spec, not discuss exposing v2 to SQL tables like the following, right ? CREATE TABLE prod.db.sample (

Re: [VOTE] Adopt the v2 spec changes

(non-binding) +1, this looks like a clean cut to me. We have been testing v2 internally for quite a while now, hopefully it can become the new default version soon to enable row level delete and update. -Jack Ye On Tue, Jul 27, 2021 at 9:59 AM Ryan Blue wrote: > I’d like to propose that we ado

[VOTE] Adopt the v2 spec changes

I’d like to propose that we adopt the pending v2 spec changes as the supported v2 spec. The full list of changes is documented in the v2 summary section of the spec . The major breaking change is the addition of delete files and metadata to track delete