Re: [DISCUSS] Restructuring Docs side navigation

Hi all, Robin has opened https://github.com/apache/iceberg/pull/13491 to refactor left-hand navigation. Please help review and share your thoughts there. Thanks, Manu On Sat, Jun 7, 2025 at 7:08 AM Kevin Liu wrote: > Thanks for starting this conversation, Manu! I agree 100%. Having > well-org

Re: cleanExpiredMetadata in RemoveSnapshots

Thank you all for taking a look and sharing your opinions! It seems we have consensus to extend the Spark procedure with a parameter to control this functionality. Let me prepare a PR for this and get back to you. Also I'll take a look at Flink usage too. Regards, Gabor Kaszab Jean-Baptiste Onof

[DISCUSS] Critical FileIO Resource Management Issue - PR #12868

Hi team, PR #12868 addresses a critical issue regarding FileIO resource management in Spark that requires broader community discussion and review. Issue Summary: When Spark cleans up broadcast variables, calling FileIO.close() can unintentionally sh

[Discuss] Proposal to support set(metadata) on TableOperations

Hey Iceberg devs: While implementing the overwrite option for registering an external table (see PR12228), I realized we might want to evaluate the option to add a new method *set(metadata)* on TableOperations interfaces for unconditionally set latest table metadata. After some discussions with

Re: cleanExpiredMetadata in RemoveSnapshots

Hi I think it makes sense to have a procedure in spark for that. My point was about the catalog long term solution. So short term, +1 for a spark procedure. Long term, we should not forget the catalog (especially for engine interoperability). Thanks! Regards JB Le lun. 7 juil. 2025 à 09:31, Gá

Re: [DISCUSS] v4 - Improved column statistics

Hey everyone, I've just added an event to the dev calendar for July 15 at 9am (PT) to discuss the column stats proposal. Eduard On Tue, Jul 8, 2025 at 4:09 AM Jacky Lee wrote: > +1 for the wonderful feature. Please count me in if you need any help. > > Gábor Kaszab 于2025年7月7日周一 21:22写道： > >

Re: [DISCUSS] Replace table transaction in REST Catalog

If we agree that there should not be constraints on the new state of the table, does this imply the updateTable API could be used to reset the new metadata.json to any arbitrary state? In which case, vendors could reset the metadata.json to the same state as when a net new table is created (providi