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: [DISCUSS] Moving to apache-iceberg Slack workspace

That's a great idea, Jacques. I agree that the Slack community should be controlled by the PMC. On Wed, Jul 28, 2021 at 10:41 AM Jacques Nadeau wrote: > My one recommendation would be that if you go off Apache infra that you > make sure all the PMC members are admins of the new account. > > On W

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: [DISCUSS] Moving to apache-iceberg Slack workspace

My one recommendation would be that if you go off Apache infra that you make sure all the PMC members are admins of the new account. On Wed, Jul 28, 2021 at 8:35 AM Ryan Blue wrote: > No problem, the site hasn't been deployed yet. > > I've also looked a bit into the invite issue for the apache-i

Re: [DISCUSS] UUID type

The original reason why I added UUID to the spec was that I thought there would be opportunities to take advantage of UUIDs as unique values and to optimize the use of UUIDs. I was thinking about auto-increment ID fields and how we might do something similar in Iceberg. The reason we have thought

Re: [DISCUSS] UUID type

Without time based uuid's as a special type I think these aren't as useful, since the only comparator that works on a non time UUID is equality. For TimeUUIDs you need another comparator (and type) since they are not lexicographically comparable but then you can actually benefit from range pred

Re: [DISCUSS] Moving to apache-iceberg Slack workspace

No problem, the site hasn't been deployed yet. I've also looked a bit into the invite issue for the apache-iceberg community and I think we should be able to set something up so that people can invite themselves. Thanks for raising this as an issue, Piotr. I didn't realize that the shared invite U

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: [DISCUSS] Moving to apache-iceberg Slack workspace

+1 Also I merged the change, sorry if that was premature. > On Jul 28, 2021, at 10:19 AM, Eduard Tudenhoefner wrote: > > +1 moving to the apache-iceberg slack > workspace > > On Wed, Jul 28, 2021 at 5:16 PM Ryan Blue > wrote: > Yes,

Re: [DISCUSS] Moving to apache-iceberg Slack workspace

+1 from me too on moving to the apache-iceberg Slack space. Thanks On Wed, Jul 28, 2021 at 8:19 AM Eduard Tudenhoefner wrote: > +1 moving to the apache-iceberg slack > workspace > > On Wed, Jul 28, 2021 at 5:16 PM Ryan Blue wrote: > >> Yes, we can update the

Re: [DISCUSS] Moving to apache-iceberg Slack workspace

+1 moving to the apache-iceberg slack workspace On Wed, Jul 28, 2021 at 5:16 PM Ryan Blue wrote: > Yes, we can update the Slack link. But we want to give everyone a chance > to speak up either in support or not before we make changes to how we > recommend comm

Re: [DISCUSS] Moving to apache-iceberg Slack workspace

Yes, we can update the Slack link. But we want to give everyone a chance to speak up either in support or not before we make changes to how we recommend communicating in the community. If you're in favor of moving to the apache-iceberg Slack space, please speak up! Ryan On Wed, Jul 28, 2021 at 1

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: [DISCUSS] Moving to apache-iceberg Slack workspace

Could we just update the slack link to https://join.slack.com/t/apache-iceberg/ on the website (see PR#2882 )? On Wed, Jul 28, 2021 at 7:13 AM Jack Ye wrote: > Any updates on this? Given the fact of the currently broken invitation > link, I think we s