Materialized Views: Next Steps

2024-05-06 Thread Walaa Eldin Moustafa
Hi Everyone, Thanks again for participating in the modeling discussion [1]. Since the outcome of this discussion was to model materialized views as separate objects, an Iceberg view and a table, I think the next step should be discussing the metadata details for each object. I have created a PR ht

Re: [VOTE] Release Apache Iceberg 1.5.2 RC0

2024-05-06 Thread Daniel Weeks
+1 (binding) Verified sigs/sums/license/build/test (Java 17) -Dan On Mon, May 6, 2024 at 11:00 AM Russell Spitzer wrote: > +1 (binding) > > Checked all the normal things > Tests > Rat > Checksum > Internal Tests > > > On May 6, 2024, at 5:35 AM, Cheng Pan wrote: > > > > +1 (non-binding) > > >

Re: Exploring Nessie Integration for Iceberg Tables: Insights Needed

2024-05-06 Thread Pani Dhakshnamurthy
Thanks Alex, please find my in-line answers: 1. When you say having both catalogs side by side, are you planning to have the same tables in both catalogs? This could be tricky consistency wise as writes would need only update one catalog. *-- My understanding is that Nessie primarily integrates

Re: Exploring Nessie Integration for Iceberg Tables: Insights Needed

2024-05-06 Thread Alex Merced
A few questions/thoughts: 1. When you say having both catalogs side by side, are you planning to have the same tables in both catalogs? This could be tricky consistency wise as writes would need only update one catalog. 2. The main reason to have a Nessie catalog would be for its catalog versioni

Exploring Nessie Integration for Iceberg Tables: Insights Needed

2024-05-06 Thread Pani Dhakshnamurthy
Hello Everyone, I'm currently planning to build a Lakehouse solution, leveraging Apache Spark and Hive Metastore in my Hadoop workflows. I'm also exploring the potential benefits of integrating Nessie as my catalog solution. With this setup, we'll have two catalogs, and we anticipate working with

Re: [Proposal] Add support for Flink Maintenance in Iceberg

2024-05-06 Thread Russell Spitzer
+1 I'm mostly in favor of the single pipeline model but I don't see any issue with supporting both models. > On May 6, 2024, at 1:43 PM, Rodrigo Meneses wrote: > > +1 > Thanks so much for driving this Peter! > > On Fri, May 3, 2024 at 11:30 AM Péter Váry >

Re: [Proposal] Add support for Flink Maintenance in Iceberg

2024-05-06 Thread Rodrigo Meneses
+1 Thanks so much for driving this Peter! On Fri, May 3, 2024 at 11:30 AM Péter Váry wrote: > Hi everyone, > > I would like to make a proposal [1] to support Flink Table Maintenance in > Iceberg. The main goal is to have a solution where Flink can execute the > Maintenance Tasks as part of the s

Re: [VOTE] Release Apache Iceberg 1.5.2 RC0

2024-05-06 Thread Russell Spitzer
+1 (binding) Checked all the normal things Tests Rat Checksum Internal Tests > On May 6, 2024, at 5:35 AM, Cheng Pan wrote: > > +1 (non-binding) > > Integrated with Apache Kyuubi[1], the CI covers > > - Iceberg Spark 3.3-3.5 with Scala 2.12 > - Iceberg Spark 3.5 with Scala 2.13 > > [1] https

Re: [Proposal] Add support for Flink Maintenance in Iceberg

2024-05-06 Thread Ferenc Csaky
+1 for the proposal, thanks for driving this! Best, Ferenc On Sunday, 5 May 2024 at 01:58, Steven Wu wrote: > +1 for the proposal of adding more table maintenance to Flink. > > It is great that the maintenance actions can be run in two modes: (1) > embedded in the Flink writer job as post comm

RE: [VOTE] Release Apache Iceberg 1.5.2 RC0

2024-05-06 Thread Cheng Pan
+1 (non-binding) Integrated with Apache Kyuubi[1], the CI covers - Iceberg Spark 3.3-3.5 with Scala 2.12 - Iceberg Spark 3.5 with Scala 2.13 [1] https://github.com/apache/kyuubi/pull/6361 Thanks, Cheng Pan On 2024/05/01 17:25:08 Amogh Jahagirdar wrote: > Hi Everyone, > > I propose that we rel