Re: [DISCUSS] Content of Iceberg 1.1.0 release

Hey Everyone, Let me give you a quick update on the status of releasing 1.1.0. We did a cut last Thursday from latest master but then I was a bit overwhelmed to continue with the next steps right away. Well, this has been days ago now and it sounds reasonable to do another cut from a more recent s

Re: [DISCUSS] Content of Iceberg 1.1.0 release

Thanks for the quick answers, @Dmitri and @Ajantha! Let's proceed then with the release creation. I'll start doing the preparations and once I get to the point to make a cut I'll use the latest git hash we have by that time. I heard that there are hiccups with the snapshot versions

Re: [DISCUSS] Content of Iceberg 1.1.0 release

> > 2) https://github.com/apache/iceberg/pull/4826 > *@Ajantha* Similar question: you pinged me to put this into 1.1.0 but as > I see this has been ongoing since May. Do you feel this is going to be > merged soon? Yeah, Let's not block the 1.1.0 release because of it. I will follow up with the re

Re: [DISCUSS] Content of Iceberg 1.1.0 release

> 1) https://github.com/apache/iceberg/issues/6031 *> @Dmitri* Could you please give us an update about this? Can we expect this to be closed in the next - let's say - week? Next week looks too iffy to me at this point. Let's not block 1.1 on this. Cheers, Dmitri. On Wed, Nov 2, 2022 at 10:01 AM

Re: [DISCUSS] Content of Iceberg 1.1.0 release

Thanks for the inputs! @Yufei As I see #6026 was merged recently so this should be fine. There are 2 outstanding items targeted for 1.1.0: 1) https://github.com/apache/iceberg/issues/6031 *@Dmitri* Could you please give us an update about this? Can we expect this to be closed in the next - let's

Re: [DISCUSS] Content of Iceberg 1.1.0 release

Hi Gabor, https://github.com/apache/iceberg/pull/6026 is fixing a bug in MOR vectorized read. We will need it in the new release. Best, Yufei `This is not a contribution` On Fri, Oct 21, 2022 at 9:26 AM Dmitri Bourlatchkov < dmitri.bourlatch...@

Re: [DISCUSS] Content of Iceberg 1.1.0 release

#6031 is wide, but not all of that is needed to be able to use the new API in Iceberg :) ATM I'm thinking about 1 week for making client-side changes available in Nessie. How frequent are Iceberg releases going to be? If they are on the order of 1-2 weeks, then of course we can defer to a later p

Re: [DISCUSS] Content of Iceberg 1.1.0 release

@Dmitri: how close to completion is #6031? We're planning to release more frequently than we have done in the past and 1.1.0 will contain the latest changes from master btw. I don't think we want to hold off too long with the release as there are quite a big amount of new things that we'd like to s

Re: [DISCUSS] Content of Iceberg 1.1.0 release

I'd like to add https://github.com/apache/iceberg/issues/6031 to the 1.1 milestone (I believe permissions are indeed required for that). Most of the work will happen on the Nessie side. When the new API is ready, the expectation is that Iceberg will simply need to compile with a new version of Nes