Re: Iceberg disaster recovery and relative path sync-up

2021-09-17 Thread Anurag Mantripragada
Hi everyone, Thanks for sharing your ideas and suggestions on this thread. I believe we have consensus on supporting multiple roots for a table and storing relative paths in metadata. We can start by adding this support in the initial phase. Yufei and I have updated the design doc[1] with the

Re: [DISCUSS] UUID type

2021-09-17 Thread Jacques Nadeau
I already added it to Substrait because of Iceberg lazy consensus :D On Fri, Sep 17, 2021 at 2:05 PM Ryan Blue wrote: > Let's move forward with it. I'm not hearing much dissent after saying the > general trend is to keep UUID. So let's call it lazy consensus. > > Ryan > > On Fri, Sep 17, 2021 a

Re: [DISCUSS] UUID type

2021-09-17 Thread Ryan Blue
Let's move forward with it. I'm not hearing much dissent after saying the general trend is to keep UUID. So let's call it lazy consensus. Ryan On Fri, Sep 17, 2021 at 1:32 PM Piotr Findeisen wrote: > Hi Ryan, > > Please advise whatever feels more appropriate from your perspective. > From my per

Re: [DISCUSS] Iceberg roadmap

2021-09-17 Thread Kyle Bendickson
This list looks overall pretty good to me. +1 For Flink 1.13 upgrade, I suggest we consider starting another thread for it. There are some open PRs, but they have outstanding questions. Specifically, dropping support for Flink 1.12 or not. I think we can upgrade without dropping support for Fli

Re: [DISCUSS] UUID type

2021-09-17 Thread Piotr Findeisen
Hi Ryan, Please advise whatever feels more appropriate from your perspective. >From my perspective, we could just go ahead and merge Trino Iceberg support for UUID, since this is just fulfilling the spec as it is defined today. Best PF On Wed, Sep 15, 2021 at 10:17 PM Ryan Blue wrote: > I don