RewriteDataFiles with merging equality deletes

Hi All! I've encountered some issues when using the rewrite operation with delete and would like to seek advice from you all. The problem description and detailed reproduction steps are recorded here: https://github.com/apache/iceberg/issues/12838. How can I avoid this problem? Thanks! Wenchi

Re: [VOTE] Minor clarification for Geo Spec

The clarification is simple and clear from the writer's perspective. CMIW, the implication is that reader should drop bbox with any NaN value regardless of the coordinate axis (in case of a writer bug). On Wed, May 7, 2025 at 6:21 AM Huang-Hsiang Cheng wrote: > +1 (non-binding) > > On May 6, 20

Re: [VOTE] Minor clarification for Geo Spec

+1 (non-binding) > On May 6, 2025, at 2:53 PM, Ryan Blue wrote: > > +1 (binding) > > Thanks to Jia and Szehon for the quick turn-around getting this done! > > On Tue, May 6, 2025 at 2:37 PM Jia Yu > wrote: >> +1 (non-binding) >> >> Thanks for putting this together! >

Re: [VOTE] Minor clarification for Geo Spec

+1 (binding) Thanks to Jia and Szehon for the quick turn-around getting this done! On Tue, May 6, 2025 at 2:37 PM Jia Yu wrote: > +1 (non-binding) > > Thanks for putting this together! > > Jia Yu > > On Tue, May 6, 2025 at 2:09 PM Szehon Ho wrote: > >> Hi everyone, >> >> As discussed briefly i

Re: [VOTE] Minor clarification for Geo Spec

+1 (non-binding) Thanks for putting this together! Jia Yu On Tue, May 6, 2025 at 2:09 PM Szehon Ho wrote: > Hi everyone, > > As discussed briefly in > https://lists.apache.org/thread/ncj0xjh2ct5xvovn4tzc45lkm1wbmorq, there > is a minor clarification for geo type bounds that we want to get in f

[VOTE] Minor clarification for Geo Spec

Hi everyone, As discussed briefly in https://lists.apache.org/thread/ncj0xjh2ct5xvovn4tzc45lkm1wbmorq, there is a minor clarification for geo type bounds that we want to get in for finalizing V3 spec. We want to clarify the behavior of null/NaN coordinate values in geo objects. There can be many

Re: [DISCUSS] Table Identifiers in Iceberg View Spec

In Spark, I believe that the USE commands sets the current catalog and namespace. This affects both where the view is created and how unqualified table identifiers are resolved. I also don't see an issue with saving the current catalog and namespace into the view metadata's default-catalog and de

Re: [DISCUSS] Finalizing the v3 spec

Thanks for clarification Ryan. I'm aware of the major changes, but I find it hard to go through all the related descriptions which are scattered all over the place. Manu On Tue, May 6, 2025 at 11:24 PM Ryan Blue wrote: > Manu, > > We aren't currently voting. We are discussing any outstanding i

Re: [DISCUSS] Finalizing the v3 spec

Manu, We aren't currently voting. We are discussing any outstanding items to address before we close v3 to further changes and adopt the existing v3 changes. Right now, the open item is to clarify NaN behavior in geometry and geography, PR #12956 . Th

Re: Changelog scan for table with delete files

Hi All! I would like to rekindle this conversation, as it seems to have stalled a few months ago. We at Apple are looking very much forward to this feature and would love to start working on adding the CDC read support to the Flink connector once the first version of this has been merged. This

Re: [DISCUSS] Finalizing the v3 spec

I'm wondering what changes we are voting for here. Is it everything related to https://iceberg.apache.org/spec/#version-3-extended-types-and-capabilities from the table spec? How about changes to other specs? Do we summarize all the changes in https://iceberg.apache.org/spec/#appendix-e-format-ver