Subject: [RESULT][VOTE] Release Apache Iceberg 1.5.1 RC0

Thanks everyone who participated in the vote for Release Apache Iceberg 1.5.1 RC0. The vote result is: +1: 3 (binding), 5 (non-binding) +0: 0 (binding), 0 (non-binding) -1: 0 (binding), 0 (non-binding) Therefore, the release candidate is passed. Thanks a ton everyone for helping out with verify

Re: Proposal for RESTful Data Operations

Hey Everyone, Reviving this thread to provide a quick update on the fine-grained metadata append commits. Since we landed the ContentFiles spec, we can now return to the append logic. Following our discussions above and the feedback received on the content files PR: #9717

Re: FlinkFileIO implementation

What I mean is that the FileIO implementation is determined by the catalog and the table, not by the engine. The engine should be able to use any valid FileIO implementation. On Tue, Apr 23, 2024 at 2:31 AM Péter Váry wrote: > Hi Ryan, > > The intended use of the *FlinkFileSystemIO* is to set it

Re: [VOTE] Release Apache Iceberg 1.5.1 RC0

Sorry for being late to the party! +1 (binding) - Checked checksum, signature and licenses - Ran example notebooks Kind regards, Fokko Op di 23 apr 2024 om 22:58 schre

Re: [VOTE] Release Apache Iceberg 1.5.1 RC0

+1 (non binding) * verified signature and checksums * verified RAT license check * verified build/tests passing with JDK17 * ran some manual tests on Spark 3.5 with GlueCatalog - Drew On Mon, Apr 22, 2024 at 1:31 PM Szehon Ho wrote: > +1 (binding) > > * Verify signature > * Verify checksum > *

Meeting Minutes 2024-04-17

Hey Iceberg Nation, Here are the meeting minutes from last week's meeting. Summary: We discussed fixes and improvements made to FileIO, REST catalog, PyIceberg, and Spark integration between columns and partitions, and agreed to handle them separately. We considered improvements for path encoding

Re: [Proposal] Add support for Materialized Views in Iceberg

+1 as well for separate objects. I think Netflix has proven this model works well. Exposure of the storage table can be handled either through naming convention or be hidden by the catalog, but that's more of an implementation detail. -Dan On Mon, Apr 22, 2024 at 3:00 PM Ryan Blue wrote: > +1

Re: FlinkFileIO implementation

Hi Ryan, The intended use of the *FlinkFileSystemIO* is to set it through the *Catalog*, like this: *Map props = new HashMap<>(3);* *props.put(CatalogProperties.WAREHOUSE_LOCATION, warehouse); props.put(CatalogProperties.URI, uri); props.put(CatalogProperties.FILE_IO_IMPL, Fli