Re: [VOTE] Release Apache Iceberg 1.11.0 RC1

[Aihua Xu]

I published another RC (RC4) for vote. Please help verify. We have built
RC2 and RC3 while additional missing backports and issues were identified,
so we go directly to RC4.

Thanks,
Aihua

On Thu, May 14, 2026 at 11:21 AM Kevin Liu  wrote:

> > But that #15470 is still stabilising, and last minute fixes are always
> dangerous as devs don't get enough time to play with them. It makes for a
> dangerous last-minute patch
>
> +1 I don't think we should wait for this. But i'll defer to the RM to make
> the call
>
> On Thu, May 14, 2026 at 9:41 AM Aihua Xu  wrote:
>
>> We got the final Spark backport, #16303
>> , merged late last night.
>> Thanks to everyone who helped make that happen.
>> At this point, there are no remaining 1.11.0 blockers listed in the
>> milestone  .
>>
>> Thanks, Steve, for raising the SerializableFileIOWithSize concern—it's a
>> valid point from a stabilization perspective to introduce #15470. As I
>> understand from the conversion (please chime in if you have more context),
>> it's not considered a regression and I think we should move forward and cut
>> the next release candidate. Please let me know your thoughts.
>>
>>
>> On Thu, May 14, 2026 at 6:08 AM Steve Loughran 
>> wrote:
>>
>>>
>>> fixing SerializableFileIOWithSize,
>>> https://github.com/apache/iceberg/pull/16284, makes that file length
>>> more of an issue, especially with the GCS file io, which uses the supplied
>>> file length to limit its range.
>>>
>>> But that #15470 is still stabilising, and last minute fixes are always
>>> dangerous as devs don't get enough time to play with them. It makes for a
>>> dangerous last-minute patch
>>>
>>> On Wed, 13 May 2026 at 05:46, huaxin gao  wrote:
>>>
 This is a correctness issue, but it is not a new regression; the same
 issue already exists in 1.10. The PR description lists Trino, Impala,
 Comet, and iceberg-rust as affected readers. I wouldn’t call it a hard
 blocker for 1.11.0 because it is a pre-existing problem.

 Thanks,
 Huaxin

 On Tue, May 12, 2026 at 8:44 PM Aihua Xu  wrote:

> Huaxin, how critical is this one? The bug has been reported for a
> while and it's still being worked on. Can you add to the milestone 1.11.0
> if it's a blocker so we can track?
>
> One more PR to consider: https://github.com/apache/iceberg/pull/15470 
> fixes
>> a correctness issue in rewriteTablePath, where manifests can record
>> stale file_size_in_bytes values for rewritten position delete files.
>> We probably want to include this fix in 1.11 too.
>
>
> On Tue, May 12, 2026 at 7:33 PM Aihua Xu  wrote:
>
>> If it’s needed, I will wait for it. Thanks for working on them.
>>
>> On May 12, 2026, at 7:17 PM, Kevin Liu  wrote:
>>
>> 
>> 3 of the PRs have been merged. Thank you Huaxin for the review. I
>> merged it since it was mostly clean backports and only targets spark 3.4.
>> The last PR is pending CI and also a clean backport,
>> https://github.com/apache/iceberg/pull/16311
>>
>>
>>
>> On Tue, May 12, 2026 at 6:52 PM Kevin Liu 
>> wrote:
>>
>>> I'll take a look at https://github.com/apache/iceberg/pull/15470
>>>
>>> Here's the Spark 3.4 PRs. I only backported PRs with relevant code
>>> changes:
>>> https://github.com/apache/iceberg/pull/16306 (Backport of #14483 +
>>> #14497)
>>> https://github.com/apache/iceberg/pull/16307 (Backport of #15683 +
>>> #16284)
>>> https://github.com/apache/iceberg/pull/16308 (Backport of #15832)
>>> https://github.com/apache/iceberg/pull/16311 (Backport of #15992)
>>> This one needs to rebase #16307 above
>>>
>>> They are mostly clean backports, some with minimal change. The first
>>> 3 already passed CI.
>>> I would like to have these in. But will defer to Aihua (RM) for the
>>> final call.
>>>
>>> Best,
>>> Kevin Liu
>>>
>>>
>>>
>>>
>>> On Tue, May 12, 2026 at 6:39 PM Manu Zhang 
>>> wrote:
>>>
 Hi Aihua,

 Since we plan to drop Spark 3.4 after 1.11.0, let's get the
 back-port PRs in. Otherwise, it will be left in a broken state.

 Thanks,
 Manu

 On Wed, May 13, 2026 at 9:16 AM Aihua Xu  wrote:

> Thanks everyone for driving these blockers to closure.
>
> Kevin, since this isn’t blocking and Spark 3.4 is deprecated, I’d
> like to go ahead and cut the next release candidate tonight so we can 
> move
> forward—unless anyone disagrees. If we end up needing another RC, we 
> can
> consider adding them in. What do you think?
>
>
> On Tue, May 12, 2026 at 4:48 PM Kevin Liu 
> wrote:
>
>> Ajay's email was stuck in webmod, i just unblo

Re: [VOTE] Release Apache Iceberg 1.11.0 RC1

[Kevin Liu]

> But that #15470 is still stabilising, and last minute fixes are always
dangerous as devs don't get enough time to play with them. It makes for a
dangerous last-minute patch

+1 I don't think we should wait for this. But i'll defer to the RM to make
the call

On Thu, May 14, 2026 at 9:41 AM Aihua Xu  wrote:

> We got the final Spark backport, #16303
> , merged late last night.
> Thanks to everyone who helped make that happen.
> At this point, there are no remaining 1.11.0 blockers listed in the
> milestone  .
>
> Thanks, Steve, for raising the SerializableFileIOWithSize concern—it's a
> valid point from a stabilization perspective to introduce #15470. As I
> understand from the conversion (please chime in if you have more context),
> it's not considered a regression and I think we should move forward and cut
> the next release candidate. Please let me know your thoughts.
>
>
> On Thu, May 14, 2026 at 6:08 AM Steve Loughran 
> wrote:
>
>>
>> fixing SerializableFileIOWithSize,
>> https://github.com/apache/iceberg/pull/16284, makes that file length
>> more of an issue, especially with the GCS file io, which uses the supplied
>> file length to limit its range.
>>
>> But that #15470 is still stabilising, and last minute fixes are always
>> dangerous as devs don't get enough time to play with them. It makes for a
>> dangerous last-minute patch
>>
>> On Wed, 13 May 2026 at 05:46, huaxin gao  wrote:
>>
>>> This is a correctness issue, but it is not a new regression; the same
>>> issue already exists in 1.10. The PR description lists Trino, Impala,
>>> Comet, and iceberg-rust as affected readers. I wouldn’t call it a hard
>>> blocker for 1.11.0 because it is a pre-existing problem.
>>>
>>> Thanks,
>>> Huaxin
>>>
>>> On Tue, May 12, 2026 at 8:44 PM Aihua Xu  wrote:
>>>
 Huaxin, how critical is this one? The bug has been reported for a while
 and it's still being worked on. Can you add to the milestone 1.11.0 if it's
 a blocker so we can track?

 One more PR to consider: https://github.com/apache/iceberg/pull/15470 fixes
> a correctness issue in rewriteTablePath, where manifests can record
> stale file_size_in_bytes values for rewritten position delete files.
> We probably want to include this fix in 1.11 too.


 On Tue, May 12, 2026 at 7:33 PM Aihua Xu  wrote:

> If it’s needed, I will wait for it. Thanks for working on them.
>
> On May 12, 2026, at 7:17 PM, Kevin Liu  wrote:
>
> 
> 3 of the PRs have been merged. Thank you Huaxin for the review. I
> merged it since it was mostly clean backports and only targets spark 3.4.
> The last PR is pending CI and also a clean backport,
> https://github.com/apache/iceberg/pull/16311
>
>
>
> On Tue, May 12, 2026 at 6:52 PM Kevin Liu 
> wrote:
>
>> I'll take a look at https://github.com/apache/iceberg/pull/15470
>>
>> Here's the Spark 3.4 PRs. I only backported PRs with relevant code
>> changes:
>> https://github.com/apache/iceberg/pull/16306 (Backport of #14483 +
>> #14497)
>> https://github.com/apache/iceberg/pull/16307 (Backport of #15683 +
>> #16284)
>> https://github.com/apache/iceberg/pull/16308 (Backport of #15832)
>> https://github.com/apache/iceberg/pull/16311 (Backport of #15992)
>> This one needs to rebase #16307 above
>>
>> They are mostly clean backports, some with minimal change. The first
>> 3 already passed CI.
>> I would like to have these in. But will defer to Aihua (RM) for the
>> final call.
>>
>> Best,
>> Kevin Liu
>>
>>
>>
>>
>> On Tue, May 12, 2026 at 6:39 PM Manu Zhang 
>> wrote:
>>
>>> Hi Aihua,
>>>
>>> Since we plan to drop Spark 3.4 after 1.11.0, let's get the
>>> back-port PRs in. Otherwise, it will be left in a broken state.
>>>
>>> Thanks,
>>> Manu
>>>
>>> On Wed, May 13, 2026 at 9:16 AM Aihua Xu  wrote:
>>>
 Thanks everyone for driving these blockers to closure.

 Kevin, since this isn’t blocking and Spark 3.4 is deprecated, I’d
 like to go ahead and cut the next release candidate tonight so we can 
 move
 forward—unless anyone disagrees. If we end up needing another RC, we 
 can
 consider adding them in. What do you think?


 On Tue, May 12, 2026 at 4:48 PM Kevin Liu 
 wrote:

> Ajay's email was stuck in webmod, i just unblocked it.
>
> Looks like all the issues in this email chain have been resolved.
> - first row ID https://github.com/apache/iceberg/pull/16263
> - analyticscore https://github.com/apache/iceberg/pull/16258
> - SerializableFileIOWithSize
> https://github.com/apache/iceberg/pull/16284
>
> Thanks everyone for contribut

Re: [VOTE] Release Apache Iceberg 1.11.0 RC1

[Aihua Xu]

We got the final Spark backport, #16303
, merged late last night.
Thanks to everyone who helped make that happen.
At this point, there are no remaining 1.11.0 blockers listed in the
milestone  .

Thanks, Steve, for raising the SerializableFileIOWithSize concern—it's a
valid point from a stabilization perspective to introduce #15470. As I
understand from the conversion (please chime in if you have more context),
it's not considered a regression and I think we should move forward and cut
the next release candidate. Please let me know your thoughts.


On Thu, May 14, 2026 at 6:08 AM Steve Loughran  wrote:

>
> fixing SerializableFileIOWithSize,
> https://github.com/apache/iceberg/pull/16284, makes that file length more
> of an issue, especially with the GCS file io, which uses the supplied file
> length to limit its range.
>
> But that #15470 is still stabilising, and last minute fixes are always
> dangerous as devs don't get enough time to play with them. It makes for a
> dangerous last-minute patch
>
> On Wed, 13 May 2026 at 05:46, huaxin gao  wrote:
>
>> This is a correctness issue, but it is not a new regression; the same
>> issue already exists in 1.10. The PR description lists Trino, Impala,
>> Comet, and iceberg-rust as affected readers. I wouldn’t call it a hard
>> blocker for 1.11.0 because it is a pre-existing problem.
>>
>> Thanks,
>> Huaxin
>>
>> On Tue, May 12, 2026 at 8:44 PM Aihua Xu  wrote:
>>
>>> Huaxin, how critical is this one? The bug has been reported for a while
>>> and it's still being worked on. Can you add to the milestone 1.11.0 if it's
>>> a blocker so we can track?
>>>
>>> One more PR to consider: https://github.com/apache/iceberg/pull/15470 fixes
 a correctness issue in rewriteTablePath, where manifests can record
 stale file_size_in_bytes values for rewritten position delete files.
 We probably want to include this fix in 1.11 too.
>>>
>>>
>>> On Tue, May 12, 2026 at 7:33 PM Aihua Xu  wrote:
>>>
 If it’s needed, I will wait for it. Thanks for working on them.

 On May 12, 2026, at 7:17 PM, Kevin Liu  wrote:

 
 3 of the PRs have been merged. Thank you Huaxin for the review. I
 merged it since it was mostly clean backports and only targets spark 3.4.
 The last PR is pending CI and also a clean backport,
 https://github.com/apache/iceberg/pull/16311



 On Tue, May 12, 2026 at 6:52 PM Kevin Liu 
 wrote:

> I'll take a look at https://github.com/apache/iceberg/pull/15470
>
> Here's the Spark 3.4 PRs. I only backported PRs with relevant code
> changes:
> https://github.com/apache/iceberg/pull/16306 (Backport of #14483 +
> #14497)
> https://github.com/apache/iceberg/pull/16307 (Backport of #15683 +
> #16284)
> https://github.com/apache/iceberg/pull/16308 (Backport of #15832)
> https://github.com/apache/iceberg/pull/16311 (Backport of #15992)
> This one needs to rebase #16307 above
>
> They are mostly clean backports, some with minimal change. The first 3
> already passed CI.
> I would like to have these in. But will defer to Aihua (RM) for the
> final call.
>
> Best,
> Kevin Liu
>
>
>
>
> On Tue, May 12, 2026 at 6:39 PM Manu Zhang 
> wrote:
>
>> Hi Aihua,
>>
>> Since we plan to drop Spark 3.4 after 1.11.0, let's get the back-port
>> PRs in. Otherwise, it will be left in a broken state.
>>
>> Thanks,
>> Manu
>>
>> On Wed, May 13, 2026 at 9:16 AM Aihua Xu  wrote:
>>
>>> Thanks everyone for driving these blockers to closure.
>>>
>>> Kevin, since this isn’t blocking and Spark 3.4 is deprecated, I’d
>>> like to go ahead and cut the next release candidate tonight so we can 
>>> move
>>> forward—unless anyone disagrees. If we end up needing another RC, we can
>>> consider adding them in. What do you think?
>>>
>>>
>>> On Tue, May 12, 2026 at 4:48 PM Kevin Liu 
>>> wrote:
>>>
 Ajay's email was stuck in webmod, i just unblocked it.

 Looks like all the issues in this email chain have been resolved.
 - first row ID https://github.com/apache/iceberg/pull/16263
 - analyticscore https://github.com/apache/iceberg/pull/16258
 - SerializableFileIOWithSize
 https://github.com/apache/iceberg/pull/16284

 Thanks everyone for contributing to the fix!

 The 1.11.0 milestone is 100% complete at this time,
 https://github.com/apache/iceberg/milestone/59

 One _last_ thing, I went over the potential feature parity gap
 between the four different Spark versions we currently support. It 
 looks
 like there are a couple of PRs that can be backported to Spark 3.4 but
 haven't been. Since this is the last release that s

Re: [VOTE] Release Apache Iceberg 1.11.0 RC1

[Steve Loughran]

fixing SerializableFileIOWithSize,
https://github.com/apache/iceberg/pull/16284, makes that file length more
of an issue, especially with the GCS file io, which uses the supplied file
length to limit its range.

But that #15470 is still stabilising, and last minute fixes are always
dangerous as devs don't get enough time to play with them. It makes for a
dangerous last-minute patch

On Wed, 13 May 2026 at 05:46, huaxin gao  wrote:

> This is a correctness issue, but it is not a new regression; the same
> issue already exists in 1.10. The PR description lists Trino, Impala,
> Comet, and iceberg-rust as affected readers. I wouldn’t call it a hard
> blocker for 1.11.0 because it is a pre-existing problem.
>
> Thanks,
> Huaxin
>
> On Tue, May 12, 2026 at 8:44 PM Aihua Xu  wrote:
>
>> Huaxin, how critical is this one? The bug has been reported for a while
>> and it's still being worked on. Can you add to the milestone 1.11.0 if it's
>> a blocker so we can track?
>>
>> One more PR to consider: https://github.com/apache/iceberg/pull/15470 fixes
>>> a correctness issue in rewriteTablePath, where manifests can record
>>> stale file_size_in_bytes values for rewritten position delete files. We
>>> probably want to include this fix in 1.11 too.
>>
>>
>> On Tue, May 12, 2026 at 7:33 PM Aihua Xu  wrote:
>>
>>> If it’s needed, I will wait for it. Thanks for working on them.
>>>
>>> On May 12, 2026, at 7:17 PM, Kevin Liu  wrote:
>>>
>>> 
>>> 3 of the PRs have been merged. Thank you Huaxin for the review. I merged
>>> it since it was mostly clean backports and only targets spark 3.4.
>>> The last PR is pending CI and also a clean backport,
>>> https://github.com/apache/iceberg/pull/16311
>>>
>>>
>>>
>>> On Tue, May 12, 2026 at 6:52 PM Kevin Liu  wrote:
>>>
 I'll take a look at https://github.com/apache/iceberg/pull/15470

 Here's the Spark 3.4 PRs. I only backported PRs with relevant code
 changes:
 https://github.com/apache/iceberg/pull/16306 (Backport of #14483 +
 #14497)
 https://github.com/apache/iceberg/pull/16307 (Backport of #15683 +
 #16284)
 https://github.com/apache/iceberg/pull/16308 (Backport of #15832)
 https://github.com/apache/iceberg/pull/16311 (Backport of #15992) This
 one needs to rebase #16307 above

 They are mostly clean backports, some with minimal change. The first 3
 already passed CI.
 I would like to have these in. But will defer to Aihua (RM) for the
 final call.

 Best,
 Kevin Liu




 On Tue, May 12, 2026 at 6:39 PM Manu Zhang 
 wrote:

> Hi Aihua,
>
> Since we plan to drop Spark 3.4 after 1.11.0, let's get the back-port
> PRs in. Otherwise, it will be left in a broken state.
>
> Thanks,
> Manu
>
> On Wed, May 13, 2026 at 9:16 AM Aihua Xu  wrote:
>
>> Thanks everyone for driving these blockers to closure.
>>
>> Kevin, since this isn’t blocking and Spark 3.4 is deprecated, I’d
>> like to go ahead and cut the next release candidate tonight so we can 
>> move
>> forward—unless anyone disagrees. If we end up needing another RC, we can
>> consider adding them in. What do you think?
>>
>>
>> On Tue, May 12, 2026 at 4:48 PM Kevin Liu 
>> wrote:
>>
>>> Ajay's email was stuck in webmod, i just unblocked it.
>>>
>>> Looks like all the issues in this email chain have been resolved.
>>> - first row ID https://github.com/apache/iceberg/pull/16263
>>> - analyticscore https://github.com/apache/iceberg/pull/16258
>>> - SerializableFileIOWithSize
>>> https://github.com/apache/iceberg/pull/16284
>>>
>>> Thanks everyone for contributing to the fix!
>>>
>>> The 1.11.0 milestone is 100% complete at this time,
>>> https://github.com/apache/iceberg/milestone/59
>>>
>>> One _last_ thing, I went over the potential feature parity gap
>>> between the four different Spark versions we currently support. It looks
>>> like there are a couple of PRs that can be backported to Spark 3.4 but
>>> haven't been. Since this is the last release that supports Spark 3.4, 
>>> I'd
>>> like to backport them and close the parity gap. This is completely 
>>> optional
>>> since we've already marked Spark 3.4 as deprecated, but I think it's a 
>>> good
>>> gesture for its final release.
>>>
>>> Best,
>>> Kevin Liu
>>>
>>>
>>>
>>> On Tue, May 12, 2026 at 3:57 PM Ajay Yadav  wrote:
>>>
 Hi Everyone,

 I would like to report a performance regression we've identified in
 Spark queries on Iceberg tables stored in cloud storage (tested with 
 GCS),
 which I believe should be addressed in the 1.11.0 release.

 Current SerializableFileIOWithSize drops file length, causing
 performance regression due to excessive metadata calls in Cloud 
 Storage:
 htt

Re: [VOTE] Release Apache Iceberg 1.11.0 RC1

[Aihua Xu]

Although we have created a new release candidate last night, the new
backport https://github.com/apache/iceberg/pull/16303 is not included.

Seems this one is also needed for the previous Spark release. I will wait
for this to merge and create a new one later today.

On Tue, May 12, 2026 at 10:32 PM huaxin gao  wrote:

> I think the original PR 
> was merged in main only.
>
> On Tue, May 12, 2026 at 10:25 PM Kevin Liu  wrote:
>
>> On my final check, __last__ backport from someone today
>> https://github.com/apache/iceberg/pull/16303
>>
>> On Tue, May 12, 2026 at 9:56 PM Aihua Xu  wrote:
>>
>>> Thanks Huaxin. I will proceed with the new RC then.
>>>
>>> On May 12, 2026, at 9:47 PM, huaxin gao  wrote:
>>>
>>> 
>>> This is a correctness issue, but it is not a new regression; the same
>>> issue already exists in 1.10. The PR description lists Trino, Impala,
>>> Comet, and iceberg-rust as affected readers. I wouldn’t call it a hard
>>> blocker for 1.11.0 because it is a pre-existing problem.
>>>
>>> Thanks,
>>> Huaxin
>>>
>>> On Tue, May 12, 2026 at 8:44 PM Aihua Xu  wrote:
>>>
 Huaxin, how critical is this one? The bug has been reported for a while
 and it's still being worked on. Can you add to the milestone 1.11.0 if it's
 a blocker so we can track?

 One more PR to consider: https://github.com/apache/iceberg/pull/15470 fixes
> a correctness issue in rewriteTablePath, where manifests can record
> stale file_size_in_bytes values for rewritten position delete files.
> We probably want to include this fix in 1.11 too.


 On Tue, May 12, 2026 at 7:33 PM Aihua Xu  wrote:

> If it’s needed, I will wait for it. Thanks for working on them.
>
> On May 12, 2026, at 7:17 PM, Kevin Liu  wrote:
>
> 
> 3 of the PRs have been merged. Thank you Huaxin for the review. I
> merged it since it was mostly clean backports and only targets spark 3.4.
> The last PR is pending CI and also a clean backport,
> https://github.com/apache/iceberg/pull/16311
>
>
>
> On Tue, May 12, 2026 at 6:52 PM Kevin Liu 
> wrote:
>
>> I'll take a look at https://github.com/apache/iceberg/pull/15470
>>
>> Here's the Spark 3.4 PRs. I only backported PRs with relevant code
>> changes:
>> https://github.com/apache/iceberg/pull/16306 (Backport of #14483 +
>> #14497)
>> https://github.com/apache/iceberg/pull/16307 (Backport of #15683 +
>> #16284)
>> https://github.com/apache/iceberg/pull/16308 (Backport of #15832)
>> https://github.com/apache/iceberg/pull/16311 (Backport of #15992)
>> This one needs to rebase #16307 above
>>
>> They are mostly clean backports, some with minimal change. The first
>> 3 already passed CI.
>> I would like to have these in. But will defer to Aihua (RM) for the
>> final call.
>>
>> Best,
>> Kevin Liu
>>
>>
>>
>>
>> On Tue, May 12, 2026 at 6:39 PM Manu Zhang 
>> wrote:
>>
>>> Hi Aihua,
>>>
>>> Since we plan to drop Spark 3.4 after 1.11.0, let's get the
>>> back-port PRs in. Otherwise, it will be left in a broken state.
>>>
>>> Thanks,
>>> Manu
>>>
>>> On Wed, May 13, 2026 at 9:16 AM Aihua Xu  wrote:
>>>
 Thanks everyone for driving these blockers to closure.

 Kevin, since this isn’t blocking and Spark 3.4 is deprecated, I’d
 like to go ahead and cut the next release candidate tonight so we can 
 move
 forward—unless anyone disagrees. If we end up needing another RC, we 
 can
 consider adding them in. What do you think?


 On Tue, May 12, 2026 at 4:48 PM Kevin Liu 
 wrote:

> Ajay's email was stuck in webmod, i just unblocked it.
>
> Looks like all the issues in this email chain have been resolved.
> - first row ID https://github.com/apache/iceberg/pull/16263
> - analyticscore https://github.com/apache/iceberg/pull/16258
> - SerializableFileIOWithSize
> https://github.com/apache/iceberg/pull/16284
>
> Thanks everyone for contributing to the fix!
>
> The 1.11.0 milestone is 100% complete at this time,
> https://github.com/apache/iceberg/milestone/59
>
> One _last_ thing, I went over the potential feature parity gap
> between the four different Spark versions we currently support. It 
> looks
> like there are a couple of PRs that can be backported to Spark 3.4 but
> haven't been. Since this is the last release that supports Spark 3.4, 
> I'd
> like to backport them and close the parity gap. This is completely 
> optional
> since we've already marked Spark 3.4 as deprecated, but I think it's 
> a good
> gesture for its final release.
>
>

Re: [VOTE] Release Apache Iceberg 1.11.0 RC1

[huaxin gao]

I think the original PR  was
merged in main only.

On Tue, May 12, 2026 at 10:25 PM Kevin Liu  wrote:

> On my final check, __last__ backport from someone today
> https://github.com/apache/iceberg/pull/16303
>
> On Tue, May 12, 2026 at 9:56 PM Aihua Xu  wrote:
>
>> Thanks Huaxin. I will proceed with the new RC then.
>>
>> On May 12, 2026, at 9:47 PM, huaxin gao  wrote:
>>
>> 
>> This is a correctness issue, but it is not a new regression; the same
>> issue already exists in 1.10. The PR description lists Trino, Impala,
>> Comet, and iceberg-rust as affected readers. I wouldn’t call it a hard
>> blocker for 1.11.0 because it is a pre-existing problem.
>>
>> Thanks,
>> Huaxin
>>
>> On Tue, May 12, 2026 at 8:44 PM Aihua Xu  wrote:
>>
>>> Huaxin, how critical is this one? The bug has been reported for a while
>>> and it's still being worked on. Can you add to the milestone 1.11.0 if it's
>>> a blocker so we can track?
>>>
>>> One more PR to consider: https://github.com/apache/iceberg/pull/15470 fixes
 a correctness issue in rewriteTablePath, where manifests can record
 stale file_size_in_bytes values for rewritten position delete files.
 We probably want to include this fix in 1.11 too.
>>>
>>>
>>> On Tue, May 12, 2026 at 7:33 PM Aihua Xu  wrote:
>>>
 If it’s needed, I will wait for it. Thanks for working on them.

 On May 12, 2026, at 7:17 PM, Kevin Liu  wrote:

 
 3 of the PRs have been merged. Thank you Huaxin for the review. I
 merged it since it was mostly clean backports and only targets spark 3.4.
 The last PR is pending CI and also a clean backport,
 https://github.com/apache/iceberg/pull/16311



 On Tue, May 12, 2026 at 6:52 PM Kevin Liu 
 wrote:

> I'll take a look at https://github.com/apache/iceberg/pull/15470
>
> Here's the Spark 3.4 PRs. I only backported PRs with relevant code
> changes:
> https://github.com/apache/iceberg/pull/16306 (Backport of #14483 +
> #14497)
> https://github.com/apache/iceberg/pull/16307 (Backport of #15683 +
> #16284)
> https://github.com/apache/iceberg/pull/16308 (Backport of #15832)
> https://github.com/apache/iceberg/pull/16311 (Backport of #15992)
> This one needs to rebase #16307 above
>
> They are mostly clean backports, some with minimal change. The first 3
> already passed CI.
> I would like to have these in. But will defer to Aihua (RM) for the
> final call.
>
> Best,
> Kevin Liu
>
>
>
>
> On Tue, May 12, 2026 at 6:39 PM Manu Zhang 
> wrote:
>
>> Hi Aihua,
>>
>> Since we plan to drop Spark 3.4 after 1.11.0, let's get the back-port
>> PRs in. Otherwise, it will be left in a broken state.
>>
>> Thanks,
>> Manu
>>
>> On Wed, May 13, 2026 at 9:16 AM Aihua Xu  wrote:
>>
>>> Thanks everyone for driving these blockers to closure.
>>>
>>> Kevin, since this isn’t blocking and Spark 3.4 is deprecated, I’d
>>> like to go ahead and cut the next release candidate tonight so we can 
>>> move
>>> forward—unless anyone disagrees. If we end up needing another RC, we can
>>> consider adding them in. What do you think?
>>>
>>>
>>> On Tue, May 12, 2026 at 4:48 PM Kevin Liu 
>>> wrote:
>>>
 Ajay's email was stuck in webmod, i just unblocked it.

 Looks like all the issues in this email chain have been resolved.
 - first row ID https://github.com/apache/iceberg/pull/16263
 - analyticscore https://github.com/apache/iceberg/pull/16258
 - SerializableFileIOWithSize
 https://github.com/apache/iceberg/pull/16284

 Thanks everyone for contributing to the fix!

 The 1.11.0 milestone is 100% complete at this time,
 https://github.com/apache/iceberg/milestone/59

 One _last_ thing, I went over the potential feature parity gap
 between the four different Spark versions we currently support. It 
 looks
 like there are a couple of PRs that can be backported to Spark 3.4 but
 haven't been. Since this is the last release that supports Spark 3.4, 
 I'd
 like to backport them and close the parity gap. This is completely 
 optional
 since we've already marked Spark 3.4 as deprecated, but I think it's a 
 good
 gesture for its final release.

 Best,
 Kevin Liu



 On Tue, May 12, 2026 at 3:57 PM Ajay Yadav  wrote:

> Hi Everyone,
>
> I would like to report a performance regression we've identified
> in Spark queries on Iceberg tables stored in cloud storage (tested 
> with
> GCS), which I believe should be addressed in the 1.11.0 release.
>
> Current SerializableFileIOWithSize dro

Re: [VOTE] Release Apache Iceberg 1.11.0 RC1

[Kevin Liu]

On my final check, __last__ backport from someone today
https://github.com/apache/iceberg/pull/16303

On Tue, May 12, 2026 at 9:56 PM Aihua Xu  wrote:

> Thanks Huaxin. I will proceed with the new RC then.
>
> On May 12, 2026, at 9:47 PM, huaxin gao  wrote:
>
> 
> This is a correctness issue, but it is not a new regression; the same
> issue already exists in 1.10. The PR description lists Trino, Impala,
> Comet, and iceberg-rust as affected readers. I wouldn’t call it a hard
> blocker for 1.11.0 because it is a pre-existing problem.
>
> Thanks,
> Huaxin
>
> On Tue, May 12, 2026 at 8:44 PM Aihua Xu  wrote:
>
>> Huaxin, how critical is this one? The bug has been reported for a while
>> and it's still being worked on. Can you add to the milestone 1.11.0 if it's
>> a blocker so we can track?
>>
>> One more PR to consider: https://github.com/apache/iceberg/pull/15470 fixes
>>> a correctness issue in rewriteTablePath, where manifests can record
>>> stale file_size_in_bytes values for rewritten position delete files. We
>>> probably want to include this fix in 1.11 too.
>>
>>
>> On Tue, May 12, 2026 at 7:33 PM Aihua Xu  wrote:
>>
>>> If it’s needed, I will wait for it. Thanks for working on them.
>>>
>>> On May 12, 2026, at 7:17 PM, Kevin Liu  wrote:
>>>
>>> 
>>> 3 of the PRs have been merged. Thank you Huaxin for the review. I merged
>>> it since it was mostly clean backports and only targets spark 3.4.
>>> The last PR is pending CI and also a clean backport,
>>> https://github.com/apache/iceberg/pull/16311
>>>
>>>
>>>
>>> On Tue, May 12, 2026 at 6:52 PM Kevin Liu  wrote:
>>>
 I'll take a look at https://github.com/apache/iceberg/pull/15470

 Here's the Spark 3.4 PRs. I only backported PRs with relevant code
 changes:
 https://github.com/apache/iceberg/pull/16306 (Backport of #14483 +
 #14497)
 https://github.com/apache/iceberg/pull/16307 (Backport of #15683 +
 #16284)
 https://github.com/apache/iceberg/pull/16308 (Backport of #15832)
 https://github.com/apache/iceberg/pull/16311 (Backport of #15992) This
 one needs to rebase #16307 above

 They are mostly clean backports, some with minimal change. The first 3
 already passed CI.
 I would like to have these in. But will defer to Aihua (RM) for the
 final call.

 Best,
 Kevin Liu




 On Tue, May 12, 2026 at 6:39 PM Manu Zhang 
 wrote:

> Hi Aihua,
>
> Since we plan to drop Spark 3.4 after 1.11.0, let's get the back-port
> PRs in. Otherwise, it will be left in a broken state.
>
> Thanks,
> Manu
>
> On Wed, May 13, 2026 at 9:16 AM Aihua Xu  wrote:
>
>> Thanks everyone for driving these blockers to closure.
>>
>> Kevin, since this isn’t blocking and Spark 3.4 is deprecated, I’d
>> like to go ahead and cut the next release candidate tonight so we can 
>> move
>> forward—unless anyone disagrees. If we end up needing another RC, we can
>> consider adding them in. What do you think?
>>
>>
>> On Tue, May 12, 2026 at 4:48 PM Kevin Liu 
>> wrote:
>>
>>> Ajay's email was stuck in webmod, i just unblocked it.
>>>
>>> Looks like all the issues in this email chain have been resolved.
>>> - first row ID https://github.com/apache/iceberg/pull/16263
>>> - analyticscore https://github.com/apache/iceberg/pull/16258
>>> - SerializableFileIOWithSize
>>> https://github.com/apache/iceberg/pull/16284
>>>
>>> Thanks everyone for contributing to the fix!
>>>
>>> The 1.11.0 milestone is 100% complete at this time,
>>> https://github.com/apache/iceberg/milestone/59
>>>
>>> One _last_ thing, I went over the potential feature parity gap
>>> between the four different Spark versions we currently support. It looks
>>> like there are a couple of PRs that can be backported to Spark 3.4 but
>>> haven't been. Since this is the last release that supports Spark 3.4, 
>>> I'd
>>> like to backport them and close the parity gap. This is completely 
>>> optional
>>> since we've already marked Spark 3.4 as deprecated, but I think it's a 
>>> good
>>> gesture for its final release.
>>>
>>> Best,
>>> Kevin Liu
>>>
>>>
>>>
>>> On Tue, May 12, 2026 at 3:57 PM Ajay Yadav  wrote:
>>>
 Hi Everyone,

 I would like to report a performance regression we've identified in
 Spark queries on Iceberg tables stored in cloud storage (tested with 
 GCS),
 which I believe should be addressed in the 1.11.0 release.

 Current SerializableFileIOWithSize drops file length, causing
 performance regression due to excessive metadata calls in Cloud 
 Storage:
 https://github.com/apache/iceberg/ssues/16283. The fix overrides
 InputFile newInputFile(String path, long length) to preserve file
 length and avoid unwanted 

Re: [VOTE] Release Apache Iceberg 1.11.0 RC1

[Aihua Xu]

Thanks Huaxin. I will proceed with the new RC then. On May 12, 2026, at 9:47 PM, huaxin gao  wrote:This is a correctness issue, but it is not a new regression; the same issue already exists in 1.10. The PR description lists Trino, Impala, Comet, and iceberg-rust as affected readers. I wouldn’t call it a hard blocker for 1.11.0 because it is a pre-existing problem.Thanks,Huaxin On Tue, May 12, 2026 at 8:44 PM Aihua Xu  wrote:Huaxin, how critical is this one? The bug has been reported for a while and it's still being worked on. Can you add to the milestone 1.11.0 if it's a blocker so we can track?One more PR to consider: https://github.com/apache/iceberg/pull/15470 fixes a correctness issue in rewriteTablePath, where manifests can record stale file_size_in_bytes values for rewritten position delete files. We probably want to include this fix in 1.11 too.On Tue, May 12, 2026 at 7:33 PM Aihua Xu  wrote:If it’s needed, I will wait for it. Thanks for working on them. On May 12, 2026, at 7:17 PM, Kevin Liu  wrote:3 of the PRs have been merged. Thank you Huaxin for the review. I merged it since it was mostly clean backports and only targets spark 3.4. The last PR is pending CI and also a clean backport, https://github.com/apache/iceberg/pull/16311On Tue, May 12, 2026 at 6:52 PM Kevin Liu  wrote:I'll take a look at https://github.com/apache/iceberg/pull/15470Here's the Spark 3.4 PRs. I only backported PRs with relevant code changes:https://github.com/apache/iceberg/pull/16306 (Backport of #14483 + #14497)https://github.com/apache/iceberg/pull/16307 (Backport of #15683 + #16284)https://github.com/apache/iceberg/pull/16308 (Backport of #15832)https://github.com/apache/iceberg/pull/16311 (Backport of #15992) This one needs to rebase #16307 aboveThey are mostly clean backports, some with minimal change. The first 3 already passed CI. I would like to have these in. But will defer to Aihua (RM) for the final call. Best,Kevin LiuOn Tue, May 12, 2026 at 6:39 PM Manu Zhang  wrote:Hi Aihua,Since we plan to drop Spark 3.4 after 1.11.0, let's get the back-port PRs in. Otherwise, it will be left in a broken state.Thanks,ManuOn Wed, May 13, 2026 at 9:16 AM Aihua Xu  wrote:Thanks everyone for driving these blockers to closure.Kevin, since this isn’t blocking and Spark 3.4 is deprecated, I’d like to go ahead and cut the next release candidate tonight so we can move forward—unless anyone disagrees. If we end up needing another RC, we can consider adding them in. What do you think? On Tue, May 12, 2026 at 4:48 PM Kevin Liu  wrote:Ajay's email was stuck in webmod, i just unblocked it. Looks like all the issues in this email chain have been resolved. - first row ID https://github.com/apache/iceberg/pull/16263- analyticscore https://github.com/apache/iceberg/pull/16258- SerializableFileIOWithSize https://github.com/apache/iceberg/pull/16284Thanks everyone for contributing to the fix! The 1.11.0 milestone is 100% complete at this time, https://github.com/apache/iceberg/milestone/59One _last_ thing, I went over the potential feature parity gap between the four different Spark versions we currently support. It looks like there are a couple of PRs that can be backported to Spark 3.4 but haven't been. Since this is the last release that supports Spark 3.4, I'd like to backport them and close the parity gap. This is completely optional since we've already marked Spark 3.4 as deprecated, but I think it's a good gesture for its final release.Best,Kevin LiuOn Tue, May 12, 2026 at 3:57 PM Ajay Yadav  wrote:
Hi Everyone,I would like to report a performance regression we've identified in Spark queries on Iceberg tables stored in cloud storage (tested with GCS), which I believe should be addressed in the 1.11.0 release.Current SerializableFileIOWithSize drops file length, causing performance regression due to excessive metadata calls in Cloud Storage: https://github.com/apache/iceberg/ssues/16283. The fix overrides InputFile newInputFile(String path, long length) to preserve file length and avoid unwanted metadata calls https://github.com/apache/iceberg/pull/16284On 2026/05/08 15:27:05 Péter Váry wrote:> Just to clarify:> > The following PRs are already merged to 1.11.0:> >    - https://github.com/apache/iceberg/pull/14297 - Spark: Support writing>    shredded variant in Iceberg-Spark>    - https://github.com/apache/iceberg/pull/15512 - Spark: fix delete from>    branch for canDeleteWhere where it does not resolve to the correct branch ->    WAP fix>    - https://github.com/apache/iceberg/pull/15475 - Flink: Add Nanosecond>    Precision Support for Flink-Iceberg Integration> > > The missing ones are the ones backporting those to other engine versions:> >    - For: 14297 :>   - 16241  - Bac

Re: [VOTE] Release Apache Iceberg 1.11.0 RC1

[huaxin gao]

This is a correctness issue, but it is not a new regression; the same issue
already exists in 1.10. The PR description lists Trino, Impala, Comet, and
iceberg-rust as affected readers. I wouldn’t call it a hard blocker for
1.11.0 because it is a pre-existing problem.

Thanks,
Huaxin

On Tue, May 12, 2026 at 8:44 PM Aihua Xu  wrote:

> Huaxin, how critical is this one? The bug has been reported for a while
> and it's still being worked on. Can you add to the milestone 1.11.0 if it's
> a blocker so we can track?
>
> One more PR to consider: https://github.com/apache/iceberg/pull/15470 fixes
>> a correctness issue in rewriteTablePath, where manifests can record
>> stale file_size_in_bytes values for rewritten position delete files. We
>> probably want to include this fix in 1.11 too.
>
>
> On Tue, May 12, 2026 at 7:33 PM Aihua Xu  wrote:
>
>> If it’s needed, I will wait for it. Thanks for working on them.
>>
>> On May 12, 2026, at 7:17 PM, Kevin Liu  wrote:
>>
>> 
>> 3 of the PRs have been merged. Thank you Huaxin for the review. I merged
>> it since it was mostly clean backports and only targets spark 3.4.
>> The last PR is pending CI and also a clean backport,
>> https://github.com/apache/iceberg/pull/16311
>>
>>
>>
>> On Tue, May 12, 2026 at 6:52 PM Kevin Liu  wrote:
>>
>>> I'll take a look at https://github.com/apache/iceberg/pull/15470
>>>
>>> Here's the Spark 3.4 PRs. I only backported PRs with relevant code
>>> changes:
>>> https://github.com/apache/iceberg/pull/16306 (Backport of #14483 +
>>> #14497)
>>> https://github.com/apache/iceberg/pull/16307 (Backport of #15683 +
>>> #16284)
>>> https://github.com/apache/iceberg/pull/16308 (Backport of #15832)
>>> https://github.com/apache/iceberg/pull/16311 (Backport of #15992) This
>>> one needs to rebase #16307 above
>>>
>>> They are mostly clean backports, some with minimal change. The first 3
>>> already passed CI.
>>> I would like to have these in. But will defer to Aihua (RM) for the
>>> final call.
>>>
>>> Best,
>>> Kevin Liu
>>>
>>>
>>>
>>>
>>> On Tue, May 12, 2026 at 6:39 PM Manu Zhang 
>>> wrote:
>>>
 Hi Aihua,

 Since we plan to drop Spark 3.4 after 1.11.0, let's get the back-port
 PRs in. Otherwise, it will be left in a broken state.

 Thanks,
 Manu

 On Wed, May 13, 2026 at 9:16 AM Aihua Xu  wrote:

> Thanks everyone for driving these blockers to closure.
>
> Kevin, since this isn’t blocking and Spark 3.4 is deprecated, I’d like
> to go ahead and cut the next release candidate tonight so we can move
> forward—unless anyone disagrees. If we end up needing another RC, we can
> consider adding them in. What do you think?
>
>
> On Tue, May 12, 2026 at 4:48 PM Kevin Liu 
> wrote:
>
>> Ajay's email was stuck in webmod, i just unblocked it.
>>
>> Looks like all the issues in this email chain have been resolved.
>> - first row ID https://github.com/apache/iceberg/pull/16263
>> - analyticscore https://github.com/apache/iceberg/pull/16258
>> - SerializableFileIOWithSize
>> https://github.com/apache/iceberg/pull/16284
>>
>> Thanks everyone for contributing to the fix!
>>
>> The 1.11.0 milestone is 100% complete at this time,
>> https://github.com/apache/iceberg/milestone/59
>>
>> One _last_ thing, I went over the potential feature parity gap
>> between the four different Spark versions we currently support. It looks
>> like there are a couple of PRs that can be backported to Spark 3.4 but
>> haven't been. Since this is the last release that supports Spark 3.4, I'd
>> like to backport them and close the parity gap. This is completely 
>> optional
>> since we've already marked Spark 3.4 as deprecated, but I think it's a 
>> good
>> gesture for its final release.
>>
>> Best,
>> Kevin Liu
>>
>>
>>
>> On Tue, May 12, 2026 at 3:57 PM Ajay Yadav  wrote:
>>
>>> Hi Everyone,
>>>
>>> I would like to report a performance regression we've identified in
>>> Spark queries on Iceberg tables stored in cloud storage (tested with 
>>> GCS),
>>> which I believe should be addressed in the 1.11.0 release.
>>>
>>> Current SerializableFileIOWithSize drops file length, causing
>>> performance regression due to excessive metadata calls in Cloud Storage:
>>> https://github.com/apache/iceberg/ssues/16283. The fix overrides
>>> InputFile newInputFile(String path, long length) to preserve file
>>> length and avoid unwanted metadata calls
>>> https://github.com/apache/iceberg/pull/16284
>>>
>>> On 2026/05/08 15:27:05 Péter Váry wrote:
>>> > Just to clarify:
>>> >
>>> > The following PRs are already merged to 1.11.0:
>>> >
>>> >- https://github.com/apache/iceberg/pull/14297 - Spark:
>>> Support writing
>>> >shredded variant in Iceberg-Spark
>>> >- https://github.com/apache/iceberg/pull

Re: [VOTE] Release Apache Iceberg 1.11.0 RC1

[Aihua Xu]

Huaxin, how critical is this one? The bug has been reported for a while and
it's still being worked on. Can you add to the milestone 1.11.0 if it's a
blocker so we can track?

One more PR to consider: https://github.com/apache/iceberg/pull/15470 fixes
> a correctness issue in rewriteTablePath, where manifests can record stale
> file_size_in_bytes values for rewritten position delete files. We
> probably want to include this fix in 1.11 too.


On Tue, May 12, 2026 at 7:33 PM Aihua Xu  wrote:

> If it’s needed, I will wait for it. Thanks for working on them.
>
> On May 12, 2026, at 7:17 PM, Kevin Liu  wrote:
>
> 
> 3 of the PRs have been merged. Thank you Huaxin for the review. I merged
> it since it was mostly clean backports and only targets spark 3.4.
> The last PR is pending CI and also a clean backport,
> https://github.com/apache/iceberg/pull/16311
>
>
>
> On Tue, May 12, 2026 at 6:52 PM Kevin Liu  wrote:
>
>> I'll take a look at https://github.com/apache/iceberg/pull/15470
>>
>> Here's the Spark 3.4 PRs. I only backported PRs with relevant code
>> changes:
>> https://github.com/apache/iceberg/pull/16306 (Backport of #14483 +
>> #14497)
>> https://github.com/apache/iceberg/pull/16307 (Backport of #15683 +
>> #16284)
>> https://github.com/apache/iceberg/pull/16308 (Backport of #15832)
>> https://github.com/apache/iceberg/pull/16311 (Backport of #15992) This
>> one needs to rebase #16307 above
>>
>> They are mostly clean backports, some with minimal change. The first 3
>> already passed CI.
>> I would like to have these in. But will defer to Aihua (RM) for the final
>> call.
>>
>> Best,
>> Kevin Liu
>>
>>
>>
>>
>> On Tue, May 12, 2026 at 6:39 PM Manu Zhang 
>> wrote:
>>
>>> Hi Aihua,
>>>
>>> Since we plan to drop Spark 3.4 after 1.11.0, let's get the back-port
>>> PRs in. Otherwise, it will be left in a broken state.
>>>
>>> Thanks,
>>> Manu
>>>
>>> On Wed, May 13, 2026 at 9:16 AM Aihua Xu  wrote:
>>>
 Thanks everyone for driving these blockers to closure.

 Kevin, since this isn’t blocking and Spark 3.4 is deprecated, I’d like
 to go ahead and cut the next release candidate tonight so we can move
 forward—unless anyone disagrees. If we end up needing another RC, we can
 consider adding them in. What do you think?


 On Tue, May 12, 2026 at 4:48 PM Kevin Liu 
 wrote:

> Ajay's email was stuck in webmod, i just unblocked it.
>
> Looks like all the issues in this email chain have been resolved.
> - first row ID https://github.com/apache/iceberg/pull/16263
> - analyticscore https://github.com/apache/iceberg/pull/16258
> - SerializableFileIOWithSize
> https://github.com/apache/iceberg/pull/16284
>
> Thanks everyone for contributing to the fix!
>
> The 1.11.0 milestone is 100% complete at this time,
> https://github.com/apache/iceberg/milestone/59
>
> One _last_ thing, I went over the potential feature parity gap between
> the four different Spark versions we currently support. It looks like 
> there
> are a couple of PRs that can be backported to Spark 3.4 but haven't been.
> Since this is the last release that supports Spark 3.4, I'd like to
> backport them and close the parity gap. This is completely optional since
> we've already marked Spark 3.4 as deprecated, but I think it's a good
> gesture for its final release.
>
> Best,
> Kevin Liu
>
>
>
> On Tue, May 12, 2026 at 3:57 PM Ajay Yadav  wrote:
>
>> Hi Everyone,
>>
>> I would like to report a performance regression we've identified in
>> Spark queries on Iceberg tables stored in cloud storage (tested with 
>> GCS),
>> which I believe should be addressed in the 1.11.0 release.
>>
>> Current SerializableFileIOWithSize drops file length, causing
>> performance regression due to excessive metadata calls in Cloud Storage:
>> https://github.com/apache/iceberg/ssues/16283. The fix overrides
>> InputFile newInputFile(String path, long length) to preserve file
>> length and avoid unwanted metadata calls
>> https://github.com/apache/iceberg/pull/16284
>>
>> On 2026/05/08 15:27:05 Péter Váry wrote:
>> > Just to clarify:
>> >
>> > The following PRs are already merged to 1.11.0:
>> >
>> >- https://github.com/apache/iceberg/pull/14297 - Spark: Support
>> writing
>> >shredded variant in Iceberg-Spark
>> >- https://github.com/apache/iceberg/pull/15512 - Spark: fix
>> delete from
>> >branch for canDeleteWhere where it does not resolve to the
>> correct branch -
>> >WAP fix
>> >- https://github.com/apache/iceberg/pull/15475 - Flink: Add
>> Nanosecond
>> >Precision Support for Flink-Iceberg Integration
>> >
>> >
>> > The missing ones are the ones backporting those to other engine
>> versions:
>> >
>> >- For: 14297 

Re: [VOTE] Release Apache Iceberg 1.11.0 RC1

[Aihua Xu]

If it’s needed, I will wait for it. Thanks for working on them. On May 12, 2026, at 7:17 PM, Kevin Liu  wrote:3 of the PRs have been merged. Thank you Huaxin for the review. I merged it since it was mostly clean backports and only targets spark 3.4. The last PR is pending CI and also a clean backport, https://github.com/apache/iceberg/pull/16311On Tue, May 12, 2026 at 6:52 PM Kevin Liu  wrote:I'll take a look at https://github.com/apache/iceberg/pull/15470Here's the Spark 3.4 PRs. I only backported PRs with relevant code changes:https://github.com/apache/iceberg/pull/16306 (Backport of #14483 + #14497)https://github.com/apache/iceberg/pull/16307 (Backport of #15683 + #16284)https://github.com/apache/iceberg/pull/16308 (Backport of #15832)https://github.com/apache/iceberg/pull/16311 (Backport of #15992) This one needs to rebase #16307 aboveThey are mostly clean backports, some with minimal change. The first 3 already passed CI. I would like to have these in. But will defer to Aihua (RM) for the final call. Best,Kevin LiuOn Tue, May 12, 2026 at 6:39 PM Manu Zhang  wrote:Hi Aihua,Since we plan to drop Spark 3.4 after 1.11.0, let's get the back-port PRs in. Otherwise, it will be left in a broken state.Thanks,ManuOn Wed, May 13, 2026 at 9:16 AM Aihua Xu  wrote:Thanks everyone for driving these blockers to closure.Kevin, since this isn’t blocking and Spark 3.4 is deprecated, I’d like to go ahead and cut the next release candidate tonight so we can move forward—unless anyone disagrees. If we end up needing another RC, we can consider adding them in. What do you think? On Tue, May 12, 2026 at 4:48 PM Kevin Liu  wrote:Ajay's email was stuck in webmod, i just unblocked it. Looks like all the issues in this email chain have been resolved. - first row ID https://github.com/apache/iceberg/pull/16263- analyticscore https://github.com/apache/iceberg/pull/16258- SerializableFileIOWithSize https://github.com/apache/iceberg/pull/16284Thanks everyone for contributing to the fix! The 1.11.0 milestone is 100% complete at this time, https://github.com/apache/iceberg/milestone/59One _last_ thing, I went over the potential feature parity gap between the four different Spark versions we currently support. It looks like there are a couple of PRs that can be backported to Spark 3.4 but haven't been. Since this is the last release that supports Spark 3.4, I'd like to backport them and close the parity gap. This is completely optional since we've already marked Spark 3.4 as deprecated, but I think it's a good gesture for its final release.Best,Kevin LiuOn Tue, May 12, 2026 at 3:57 PM Ajay Yadav  wrote:
Hi Everyone,I would like to report a performance regression we've identified in Spark queries on Iceberg tables stored in cloud storage (tested with GCS), which I believe should be addressed in the 1.11.0 release.Current SerializableFileIOWithSize drops file length, causing performance regression due to excessive metadata calls in Cloud Storage: https://github.com/apache/iceberg/ssues/16283. The fix overrides InputFile newInputFile(String path, long length) to preserve file length and avoid unwanted metadata calls https://github.com/apache/iceberg/pull/16284On 2026/05/08 15:27:05 Péter Váry wrote:> Just to clarify:> > The following PRs are already merged to 1.11.0:> >    - https://github.com/apache/iceberg/pull/14297 - Spark: Support writing>    shredded variant in Iceberg-Spark>    - https://github.com/apache/iceberg/pull/15512 - Spark: fix delete from>    branch for canDeleteWhere where it does not resolve to the correct branch ->    WAP fix>    - https://github.com/apache/iceberg/pull/15475 - Flink: Add Nanosecond>    Precision Support for Flink-Iceberg Integration> > > The missing ones are the ones backporting those to other engine versions:> >    - For: 14297 :>   - 16241  - Backport for>   variant shredding in Spark 4.0>    - For: 15512 :>   - 16245  - Spark:>   backport PR #15512 to v3.4, v3.5, v4.0 for WAP branch delete fix>    - For: 15475 :>   - #16183 ,  #16239>   , #16240>    - Backport for Nano>   timestamps for Flink 2.0/1.20> > > So the PRs needed on 1.11.0 are:> https://github.com/apache/iceberg/pull/16241> https://github.com/apache/iceberg/pull/16245> https://github.com/apache/iceberg/pull/16183> https://github.com/apache/iceberg/pull/16239> https://github.com/apache/iceberg/pull/16240> https://github.com/apache/iceberg/pull/16186> > Aihua Xu  ezt írta (időpont: 2026. máj. 8., P, 17:13):> > > Thank you all 

Re: Re: [VOTE] Release Apache Iceberg 1.11.0 RC1

[Kevin Liu]

3 of the PRs have been merged. Thank you Huaxin for the review. I merged it
since it was mostly clean backports and only targets spark 3.4.
The last PR is pending CI and also a clean backport,
https://github.com/apache/iceberg/pull/16311



On Tue, May 12, 2026 at 6:52 PM Kevin Liu  wrote:

> I'll take a look at https://github.com/apache/iceberg/pull/15470
>
> Here's the Spark 3.4 PRs. I only backported PRs with relevant code changes:
> https://github.com/apache/iceberg/pull/16306 (Backport of #14483 + #14497)
> https://github.com/apache/iceberg/pull/16307 (Backport of #15683 + #16284)
> https://github.com/apache/iceberg/pull/16308 (Backport of #15832)
> https://github.com/apache/iceberg/pull/16311 (Backport of #15992) This
> one needs to rebase #16307 above
>
> They are mostly clean backports, some with minimal change. The first 3
> already passed CI.
> I would like to have these in. But will defer to Aihua (RM) for the final
> call.
>
> Best,
> Kevin Liu
>
>
>
>
> On Tue, May 12, 2026 at 6:39 PM Manu Zhang 
> wrote:
>
>> Hi Aihua,
>>
>> Since we plan to drop Spark 3.4 after 1.11.0, let's get the back-port PRs
>> in. Otherwise, it will be left in a broken state.
>>
>> Thanks,
>> Manu
>>
>> On Wed, May 13, 2026 at 9:16 AM Aihua Xu  wrote:
>>
>>> Thanks everyone for driving these blockers to closure.
>>>
>>> Kevin, since this isn’t blocking and Spark 3.4 is deprecated, I’d like
>>> to go ahead and cut the next release candidate tonight so we can move
>>> forward—unless anyone disagrees. If we end up needing another RC, we can
>>> consider adding them in. What do you think?
>>>
>>>
>>> On Tue, May 12, 2026 at 4:48 PM Kevin Liu  wrote:
>>>
 Ajay's email was stuck in webmod, i just unblocked it.

 Looks like all the issues in this email chain have been resolved.
 - first row ID https://github.com/apache/iceberg/pull/16263
 - analyticscore https://github.com/apache/iceberg/pull/16258
 - SerializableFileIOWithSize
 https://github.com/apache/iceberg/pull/16284

 Thanks everyone for contributing to the fix!

 The 1.11.0 milestone is 100% complete at this time,
 https://github.com/apache/iceberg/milestone/59

 One _last_ thing, I went over the potential feature parity gap between
 the four different Spark versions we currently support. It looks like there
 are a couple of PRs that can be backported to Spark 3.4 but haven't been.
 Since this is the last release that supports Spark 3.4, I'd like to
 backport them and close the parity gap. This is completely optional since
 we've already marked Spark 3.4 as deprecated, but I think it's a good
 gesture for its final release.

 Best,
 Kevin Liu



 On Tue, May 12, 2026 at 3:57 PM Ajay Yadav  wrote:

> Hi Everyone,
>
> I would like to report a performance regression we've identified in
> Spark queries on Iceberg tables stored in cloud storage (tested with GCS),
> which I believe should be addressed in the 1.11.0 release.
>
> Current SerializableFileIOWithSize drops file length, causing
> performance regression due to excessive metadata calls in Cloud Storage:
> https://github.com/apache/iceberg/ssues/16283. The fix overrides
> InputFile newInputFile(String path, long length) to preserve file
> length and avoid unwanted metadata calls
> https://github.com/apache/iceberg/pull/16284
>
> On 2026/05/08 15:27:05 Péter Váry wrote:
> > Just to clarify:
> >
> > The following PRs are already merged to 1.11.0:
> >
> >- https://github.com/apache/iceberg/pull/14297 - Spark: Support
> writing
> >shredded variant in Iceberg-Spark
> >- https://github.com/apache/iceberg/pull/15512 - Spark: fix
> delete from
> >branch for canDeleteWhere where it does not resolve to the
> correct branch -
> >WAP fix
> >- https://github.com/apache/iceberg/pull/15475 - Flink: Add
> Nanosecond
> >Precision Support for Flink-Iceberg Integration
> >
> >
> > The missing ones are the ones backporting those to other engine
> versions:
> >
> >- For: 14297 :
> >   - 16241  -
> Backport for
> >   variant shredding in Spark 4.0
> >- For: 15512 :
> >   - 16245  -
> Spark:
> >   backport PR #15512 to v3.4, v3.5, v4.0 for WAP branch delete
> fix
> >- For: 15475 :
> >   - #16183 ,
> #16239
> >   , #16240
> >    - Backport for
> Nano
> >   timestamps for Flink 2.0/1.20
> >
> >

Re: Re: [VOTE] Release Apache Iceberg 1.11.0 RC1

[Kevin Liu]

I'll take a look at https://github.com/apache/iceberg/pull/15470

Here's the Spark 3.4 PRs. I only backported PRs with relevant code changes:
https://github.com/apache/iceberg/pull/16306 (Backport of #14483 + #14497)
https://github.com/apache/iceberg/pull/16307 (Backport of #15683 + #16284)
https://github.com/apache/iceberg/pull/16308 (Backport of #15832)
https://github.com/apache/iceberg/pull/16311 (Backport of #15992) This one
needs to rebase #16307 above

They are mostly clean backports, some with minimal change. The first 3
already passed CI.
I would like to have these in. But will defer to Aihua (RM) for the final
call.

Best,
Kevin Liu




On Tue, May 12, 2026 at 6:39 PM Manu Zhang  wrote:

> Hi Aihua,
>
> Since we plan to drop Spark 3.4 after 1.11.0, let's get the back-port PRs
> in. Otherwise, it will be left in a broken state.
>
> Thanks,
> Manu
>
> On Wed, May 13, 2026 at 9:16 AM Aihua Xu  wrote:
>
>> Thanks everyone for driving these blockers to closure.
>>
>> Kevin, since this isn’t blocking and Spark 3.4 is deprecated, I’d like to
>> go ahead and cut the next release candidate tonight so we can move
>> forward—unless anyone disagrees. If we end up needing another RC, we can
>> consider adding them in. What do you think?
>>
>>
>> On Tue, May 12, 2026 at 4:48 PM Kevin Liu  wrote:
>>
>>> Ajay's email was stuck in webmod, i just unblocked it.
>>>
>>> Looks like all the issues in this email chain have been resolved.
>>> - first row ID https://github.com/apache/iceberg/pull/16263
>>> - analyticscore https://github.com/apache/iceberg/pull/16258
>>> - SerializableFileIOWithSize
>>> https://github.com/apache/iceberg/pull/16284
>>>
>>> Thanks everyone for contributing to the fix!
>>>
>>> The 1.11.0 milestone is 100% complete at this time,
>>> https://github.com/apache/iceberg/milestone/59
>>>
>>> One _last_ thing, I went over the potential feature parity gap between
>>> the four different Spark versions we currently support. It looks like there
>>> are a couple of PRs that can be backported to Spark 3.4 but haven't been.
>>> Since this is the last release that supports Spark 3.4, I'd like to
>>> backport them and close the parity gap. This is completely optional since
>>> we've already marked Spark 3.4 as deprecated, but I think it's a good
>>> gesture for its final release.
>>>
>>> Best,
>>> Kevin Liu
>>>
>>>
>>>
>>> On Tue, May 12, 2026 at 3:57 PM Ajay Yadav  wrote:
>>>
 Hi Everyone,

 I would like to report a performance regression we've identified in
 Spark queries on Iceberg tables stored in cloud storage (tested with GCS),
 which I believe should be addressed in the 1.11.0 release.

 Current SerializableFileIOWithSize drops file length, causing
 performance regression due to excessive metadata calls in Cloud Storage:
 https://github.com/apache/iceberg/ssues/16283. The fix overrides
 InputFile newInputFile(String path, long length) to preserve file
 length and avoid unwanted metadata calls
 https://github.com/apache/iceberg/pull/16284

 On 2026/05/08 15:27:05 Péter Váry wrote:
 > Just to clarify:
 >
 > The following PRs are already merged to 1.11.0:
 >
 >- https://github.com/apache/iceberg/pull/14297 - Spark: Support
 writing
 >shredded variant in Iceberg-Spark
 >- https://github.com/apache/iceberg/pull/15512 - Spark: fix
 delete from
 >branch for canDeleteWhere where it does not resolve to the
 correct branch -
 >WAP fix
 >- https://github.com/apache/iceberg/pull/15475 - Flink: Add
 Nanosecond
 >Precision Support for Flink-Iceberg Integration
 >
 >
 > The missing ones are the ones backporting those to other engine
 versions:
 >
 >- For: 14297 :
 >   - 16241  -
 Backport for
 >   variant shredding in Spark 4.0
 >- For: 15512 :
 >   - 16245  - Spark:
 >   backport PR #15512 to v3.4, v3.5, v4.0 for WAP branch delete
 fix
 >- For: 15475 :
 >   - #16183 ,
 #16239
 >   , #16240
 >    - Backport for
 Nano
 >   timestamps for Flink 2.0/1.20
 >
 >
 > So the PRs needed on 1.11.0 are:
 > https://github.com/apache/iceberg/pull/16241
 > https://github.com/apache/iceberg/pull/16245
 > https://github.com/apache/iceberg/pull/16183
 > https://github.com/apache/iceberg/pull/16239
 > https://github.com/apache/iceberg/pull/16240
 > https://github.com/apache/iceberg/pull/16186
 >
 > Aihua Xu  ezt írta (időpont: 2026. máj. 8., P,
 17:13):
 >
>>

Re: Re: [VOTE] Release Apache Iceberg 1.11.0 RC1

[Manu Zhang]

Hi Aihua,

Since we plan to drop Spark 3.4 after 1.11.0, let's get the back-port PRs
in. Otherwise, it will be left in a broken state.

Thanks,
Manu

On Wed, May 13, 2026 at 9:16 AM Aihua Xu  wrote:

> Thanks everyone for driving these blockers to closure.
>
> Kevin, since this isn’t blocking and Spark 3.4 is deprecated, I’d like to
> go ahead and cut the next release candidate tonight so we can move
> forward—unless anyone disagrees. If we end up needing another RC, we can
> consider adding them in. What do you think?
>
>
> On Tue, May 12, 2026 at 4:48 PM Kevin Liu  wrote:
>
>> Ajay's email was stuck in webmod, i just unblocked it.
>>
>> Looks like all the issues in this email chain have been resolved.
>> - first row ID https://github.com/apache/iceberg/pull/16263
>> - analyticscore https://github.com/apache/iceberg/pull/16258
>> - SerializableFileIOWithSize https://github.com/apache/iceberg/pull/16284
>>
>> Thanks everyone for contributing to the fix!
>>
>> The 1.11.0 milestone is 100% complete at this time,
>> https://github.com/apache/iceberg/milestone/59
>>
>> One _last_ thing, I went over the potential feature parity gap between
>> the four different Spark versions we currently support. It looks like there
>> are a couple of PRs that can be backported to Spark 3.4 but haven't been.
>> Since this is the last release that supports Spark 3.4, I'd like to
>> backport them and close the parity gap. This is completely optional since
>> we've already marked Spark 3.4 as deprecated, but I think it's a good
>> gesture for its final release.
>>
>> Best,
>> Kevin Liu
>>
>>
>>
>> On Tue, May 12, 2026 at 3:57 PM Ajay Yadav  wrote:
>>
>>> Hi Everyone,
>>>
>>> I would like to report a performance regression we've identified in
>>> Spark queries on Iceberg tables stored in cloud storage (tested with GCS),
>>> which I believe should be addressed in the 1.11.0 release.
>>>
>>> Current SerializableFileIOWithSize drops file length, causing
>>> performance regression due to excessive metadata calls in Cloud Storage:
>>> https://github.com/apache/iceberg/ssues/16283. The fix overrides
>>> InputFile newInputFile(String path, long length) to preserve file
>>> length and avoid unwanted metadata calls
>>> https://github.com/apache/iceberg/pull/16284
>>>
>>> On 2026/05/08 15:27:05 Péter Váry wrote:
>>> > Just to clarify:
>>> >
>>> > The following PRs are already merged to 1.11.0:
>>> >
>>> >- https://github.com/apache/iceberg/pull/14297 - Spark: Support
>>> writing
>>> >shredded variant in Iceberg-Spark
>>> >- https://github.com/apache/iceberg/pull/15512 - Spark: fix delete
>>> from
>>> >branch for canDeleteWhere where it does not resolve to the correct
>>> branch -
>>> >WAP fix
>>> >- https://github.com/apache/iceberg/pull/15475 - Flink: Add
>>> Nanosecond
>>> >Precision Support for Flink-Iceberg Integration
>>> >
>>> >
>>> > The missing ones are the ones backporting those to other engine
>>> versions:
>>> >
>>> >- For: 14297 :
>>> >   - 16241  -
>>> Backport for
>>> >   variant shredding in Spark 4.0
>>> >- For: 15512 :
>>> >   - 16245  - Spark:
>>> >   backport PR #15512 to v3.4, v3.5, v4.0 for WAP branch delete fix
>>> >- For: 15475 :
>>> >   - #16183 ,  #16239
>>> >   , #16240
>>> >    - Backport for
>>> Nano
>>> >   timestamps for Flink 2.0/1.20
>>> >
>>> >
>>> > So the PRs needed on 1.11.0 are:
>>> > https://github.com/apache/iceberg/pull/16241
>>> > https://github.com/apache/iceberg/pull/16245
>>> > https://github.com/apache/iceberg/pull/16183
>>> > https://github.com/apache/iceberg/pull/16239
>>> > https://github.com/apache/iceberg/pull/16240
>>> > https://github.com/apache/iceberg/pull/16186
>>> >
>>> > Aihua Xu  ezt írta (időpont: 2026. máj. 8., P,
>>> 17:13):
>>> >
>>> > > Thank you all for the feedback and for verifying the release
>>> candidate.
>>> > > Based on the issues identified above, we will include the following
>>> fixes
>>> > > and cut RC2 with a new vote:
>>> > >
>>> > > https://github.com/apache/iceberg/pull/14297
>>> > > https://github.com/apache/iceberg/pull/15512
>>> > > https://github.com/apache/iceberg/pull/15475
>>> > > https://github.com/apache/iceberg/pull/16186
>>> > >
>>> > > Please let me know if you have any questions or identified additional
>>> > > issues.
>>> > >
>>> > > Thanks,
>>> > > Aihua
>>> > >
>>> > > On Thu, May 7, 2026 at 10:09 PM Aihua Xu  wrote:
>>> > >
>>> > >> I also looked into this. There is a configuration
>>> > >> gcs.analytics-core.enabled to enable/disable GCS Analytics Core. The
>>> > >> current implementation always requires runtime d

Re: Re: [VOTE] Release Apache Iceberg 1.11.0 RC1

[huaxin gao]

One more PR to consider: https://github.com/apache/iceberg/pull/15470 fixes
a correctness issue in rewriteTablePath, where manifests can record stale
file_size_in_bytes values for rewritten position delete files. We probably
want to include this fix in 1.11 too.

Thanks,

Huaxin

On Tue, May 12, 2026 at 6:16 PM Aihua Xu  wrote:

> Thanks everyone for driving these blockers to closure.
>
> Kevin, since this isn’t blocking and Spark 3.4 is deprecated, I’d like to
> go ahead and cut the next release candidate tonight so we can move
> forward—unless anyone disagrees. If we end up needing another RC, we can
> consider adding them in. What do you think?
>
>
> On Tue, May 12, 2026 at 4:48 PM Kevin Liu  wrote:
>
>> Ajay's email was stuck in webmod, i just unblocked it.
>>
>> Looks like all the issues in this email chain have been resolved.
>> - first row ID https://github.com/apache/iceberg/pull/16263
>> - analyticscore https://github.com/apache/iceberg/pull/16258
>> - SerializableFileIOWithSize https://github.com/apache/iceberg/pull/16284
>>
>> Thanks everyone for contributing to the fix!
>>
>> The 1.11.0 milestone is 100% complete at this time,
>> https://github.com/apache/iceberg/milestone/59
>>
>> One _last_ thing, I went over the potential feature parity gap between
>> the four different Spark versions we currently support. It looks like there
>> are a couple of PRs that can be backported to Spark 3.4 but haven't been.
>> Since this is the last release that supports Spark 3.4, I'd like to
>> backport them and close the parity gap. This is completely optional since
>> we've already marked Spark 3.4 as deprecated, but I think it's a good
>> gesture for its final release.
>>
>> Best,
>> Kevin Liu
>>
>>
>>
>> On Tue, May 12, 2026 at 3:57 PM Ajay Yadav  wrote:
>>
>>> Hi Everyone,
>>>
>>> I would like to report a performance regression we've identified in
>>> Spark queries on Iceberg tables stored in cloud storage (tested with GCS),
>>> which I believe should be addressed in the 1.11.0 release.
>>>
>>> Current SerializableFileIOWithSize drops file length, causing
>>> performance regression due to excessive metadata calls in Cloud Storage:
>>> https://github.com/apache/iceberg/ssues/16283. The fix overrides
>>> InputFile newInputFile(String path, long length) to preserve file
>>> length and avoid unwanted metadata calls
>>> https://github.com/apache/iceberg/pull/16284
>>>
>>> On 2026/05/08 15:27:05 Péter Váry wrote:
>>> > Just to clarify:
>>> >
>>> > The following PRs are already merged to 1.11.0:
>>> >
>>> >- https://github.com/apache/iceberg/pull/14297 - Spark: Support
>>> writing
>>> >shredded variant in Iceberg-Spark
>>> >- https://github.com/apache/iceberg/pull/15512 - Spark: fix delete
>>> from
>>> >branch for canDeleteWhere where it does not resolve to the correct
>>> branch -
>>> >WAP fix
>>> >- https://github.com/apache/iceberg/pull/15475 - Flink: Add
>>> Nanosecond
>>> >Precision Support for Flink-Iceberg Integration
>>> >
>>> >
>>> > The missing ones are the ones backporting those to other engine
>>> versions:
>>> >
>>> >- For: 14297 :
>>> >   - 16241  -
>>> Backport for
>>> >   variant shredding in Spark 4.0
>>> >- For: 15512 :
>>> >   - 16245  - Spark:
>>> >   backport PR #15512 to v3.4, v3.5, v4.0 for WAP branch delete fix
>>> >- For: 15475 :
>>> >   - #16183 ,  #16239
>>> >   , #16240
>>> >    - Backport for
>>> Nano
>>> >   timestamps for Flink 2.0/1.20
>>> >
>>> >
>>> > So the PRs needed on 1.11.0 are:
>>> > https://github.com/apache/iceberg/pull/16241
>>> > https://github.com/apache/iceberg/pull/16245
>>> > https://github.com/apache/iceberg/pull/16183
>>> > https://github.com/apache/iceberg/pull/16239
>>> > https://github.com/apache/iceberg/pull/16240
>>> > https://github.com/apache/iceberg/pull/16186
>>> >
>>> > Aihua Xu  ezt írta (időpont: 2026. máj. 8., P,
>>> 17:13):
>>> >
>>> > > Thank you all for the feedback and for verifying the release
>>> candidate.
>>> > > Based on the issues identified above, we will include the following
>>> fixes
>>> > > and cut RC2 with a new vote:
>>> > >
>>> > > https://github.com/apache/iceberg/pull/14297
>>> > > https://github.com/apache/iceberg/pull/15512
>>> > > https://github.com/apache/iceberg/pull/15475
>>> > > https://github.com/apache/iceberg/pull/16186
>>> > >
>>> > > Please let me know if you have any questions or identified additional
>>> > > issues.
>>> > >
>>> > > Thanks,
>>> > > Aihua
>>> > >
>>> > > On Thu, May 7, 2026 at 10:09 PM Aihua Xu  wrote:
>>> > >
>>> > >> I also looked into this. There is a configuration
>>> 

Re: Re: [VOTE] Release Apache Iceberg 1.11.0 RC1

[Aihua Xu]

Thanks everyone for driving these blockers to closure.

Kevin, since this isn’t blocking and Spark 3.4 is deprecated, I’d like to
go ahead and cut the next release candidate tonight so we can move
forward—unless anyone disagrees. If we end up needing another RC, we can
consider adding them in. What do you think?


On Tue, May 12, 2026 at 4:48 PM Kevin Liu  wrote:

> Ajay's email was stuck in webmod, i just unblocked it.
>
> Looks like all the issues in this email chain have been resolved.
> - first row ID https://github.com/apache/iceberg/pull/16263
> - analyticscore https://github.com/apache/iceberg/pull/16258
> - SerializableFileIOWithSize https://github.com/apache/iceberg/pull/16284
>
> Thanks everyone for contributing to the fix!
>
> The 1.11.0 milestone is 100% complete at this time,
> https://github.com/apache/iceberg/milestone/59
>
> One _last_ thing, I went over the potential feature parity gap between the
> four different Spark versions we currently support. It looks like there are
> a couple of PRs that can be backported to Spark 3.4 but haven't been. Since
> this is the last release that supports Spark 3.4, I'd like to backport them
> and close the parity gap. This is completely optional since we've already
> marked Spark 3.4 as deprecated, but I think it's a good gesture for its
> final release.
>
> Best,
> Kevin Liu
>
>
>
> On Tue, May 12, 2026 at 3:57 PM Ajay Yadav  wrote:
>
>> Hi Everyone,
>>
>> I would like to report a performance regression we've identified in Spark
>> queries on Iceberg tables stored in cloud storage (tested with GCS), which
>> I believe should be addressed in the 1.11.0 release.
>>
>> Current SerializableFileIOWithSize drops file length, causing
>> performance regression due to excessive metadata calls in Cloud Storage:
>> https://github.com/apache/iceberg/ssues/16283. The fix overrides
>> InputFile newInputFile(String path, long length) to preserve file length
>> and avoid unwanted metadata calls
>> https://github.com/apache/iceberg/pull/16284
>>
>> On 2026/05/08 15:27:05 Péter Váry wrote:
>> > Just to clarify:
>> >
>> > The following PRs are already merged to 1.11.0:
>> >
>> >- https://github.com/apache/iceberg/pull/14297 - Spark: Support
>> writing
>> >shredded variant in Iceberg-Spark
>> >- https://github.com/apache/iceberg/pull/15512 - Spark: fix delete
>> from
>> >branch for canDeleteWhere where it does not resolve to the correct
>> branch -
>> >WAP fix
>> >- https://github.com/apache/iceberg/pull/15475 - Flink: Add
>> Nanosecond
>> >Precision Support for Flink-Iceberg Integration
>> >
>> >
>> > The missing ones are the ones backporting those to other engine
>> versions:
>> >
>> >- For: 14297 :
>> >   - 16241  -
>> Backport for
>> >   variant shredding in Spark 4.0
>> >- For: 15512 :
>> >   - 16245  - Spark:
>> >   backport PR #15512 to v3.4, v3.5, v4.0 for WAP branch delete fix
>> >- For: 15475 :
>> >   - #16183 ,  #16239
>> >   , #16240
>> >    - Backport for
>> Nano
>> >   timestamps for Flink 2.0/1.20
>> >
>> >
>> > So the PRs needed on 1.11.0 are:
>> > https://github.com/apache/iceberg/pull/16241
>> > https://github.com/apache/iceberg/pull/16245
>> > https://github.com/apache/iceberg/pull/16183
>> > https://github.com/apache/iceberg/pull/16239
>> > https://github.com/apache/iceberg/pull/16240
>> > https://github.com/apache/iceberg/pull/16186
>> >
>> > Aihua Xu  ezt írta (időpont: 2026. máj. 8., P, 17:13):
>> >
>> > > Thank you all for the feedback and for verifying the release
>> candidate.
>> > > Based on the issues identified above, we will include the following
>> fixes
>> > > and cut RC2 with a new vote:
>> > >
>> > > https://github.com/apache/iceberg/pull/14297
>> > > https://github.com/apache/iceberg/pull/15512
>> > > https://github.com/apache/iceberg/pull/15475
>> > > https://github.com/apache/iceberg/pull/16186
>> > >
>> > > Please let me know if you have any questions or identified additional
>> > > issues.
>> > >
>> > > Thanks,
>> > > Aihua
>> > >
>> > > On Thu, May 7, 2026 at 10:09 PM Aihua Xu  wrote:
>> > >
>> > >> I also looked into this. There is a configuration
>> > >> gcs.analytics-core.enabled to enable/disable GCS Analytics Core. The
>> > >> current implementation always requires runtime dependency of GCS
>> Analytics
>> > >> Core even if the configuration is off. Ideally we can lazy load such
>> > >> dependency so the dependency is only required when the feature is
>> > >> explicitly enabled. But since GCP is likely to enable GCS Analytics
>> Core by
>> > >> default, I feel it's reasonable for downstream proje

Re: Re: [VOTE] Release Apache Iceberg 1.11.0 RC1

[Kevin Liu]

Ajay's email was stuck in webmod, i just unblocked it.

Looks like all the issues in this email chain have been resolved.
- first row ID https://github.com/apache/iceberg/pull/16263
- analyticscore https://github.com/apache/iceberg/pull/16258
- SerializableFileIOWithSize https://github.com/apache/iceberg/pull/16284

Thanks everyone for contributing to the fix!

The 1.11.0 milestone is 100% complete at this time,
https://github.com/apache/iceberg/milestone/59

One _last_ thing, I went over the potential feature parity gap between the
four different Spark versions we currently support. It looks like there are
a couple of PRs that can be backported to Spark 3.4 but haven't been. Since
this is the last release that supports Spark 3.4, I'd like to backport them
and close the parity gap. This is completely optional since we've already
marked Spark 3.4 as deprecated, but I think it's a good gesture for its
final release.

Best,
Kevin Liu



On Tue, May 12, 2026 at 3:57 PM Ajay Yadav  wrote:

> Hi Everyone,
>
> I would like to report a performance regression we've identified in Spark
> queries on Iceberg tables stored in cloud storage (tested with GCS), which
> I believe should be addressed in the 1.11.0 release.
>
> Current SerializableFileIOWithSize drops file length, causing performance
> regression due to excessive metadata calls in Cloud Storage:
> https://github.com/apache/iceberg/ssues/16283. The fix overrides
> InputFile newInputFile(String path, long length) to preserve file length
> and avoid unwanted metadata calls
> https://github.com/apache/iceberg/pull/16284
>
> On 2026/05/08 15:27:05 Péter Váry wrote:
> > Just to clarify:
> >
> > The following PRs are already merged to 1.11.0:
> >
> >- https://github.com/apache/iceberg/pull/14297 - Spark: Support
> writing
> >shredded variant in Iceberg-Spark
> >- https://github.com/apache/iceberg/pull/15512 - Spark: fix delete
> from
> >branch for canDeleteWhere where it does not resolve to the correct
> branch -
> >WAP fix
> >- https://github.com/apache/iceberg/pull/15475 - Flink: Add
> Nanosecond
> >Precision Support for Flink-Iceberg Integration
> >
> >
> > The missing ones are the ones backporting those to other engine versions:
> >
> >- For: 14297 :
> >   - 16241  - Backport
> for
> >   variant shredding in Spark 4.0
> >- For: 15512 :
> >   - 16245  - Spark:
> >   backport PR #15512 to v3.4, v3.5, v4.0 for WAP branch delete fix
> >- For: 15475 :
> >   - #16183 ,  #16239
> >   , #16240
> >    - Backport for Nano
> >   timestamps for Flink 2.0/1.20
> >
> >
> > So the PRs needed on 1.11.0 are:
> > https://github.com/apache/iceberg/pull/16241
> > https://github.com/apache/iceberg/pull/16245
> > https://github.com/apache/iceberg/pull/16183
> > https://github.com/apache/iceberg/pull/16239
> > https://github.com/apache/iceberg/pull/16240
> > https://github.com/apache/iceberg/pull/16186
> >
> > Aihua Xu  ezt írta (időpont: 2026. máj. 8., P, 17:13):
> >
> > > Thank you all for the feedback and for verifying the release candidate.
> > > Based on the issues identified above, we will include the following
> fixes
> > > and cut RC2 with a new vote:
> > >
> > > https://github.com/apache/iceberg/pull/14297
> > > https://github.com/apache/iceberg/pull/15512
> > > https://github.com/apache/iceberg/pull/15475
> > > https://github.com/apache/iceberg/pull/16186
> > >
> > > Please let me know if you have any questions or identified additional
> > > issues.
> > >
> > > Thanks,
> > > Aihua
> > >
> > > On Thu, May 7, 2026 at 10:09 PM Aihua Xu  wrote:
> > >
> > >> I also looked into this. There is a configuration
> > >> gcs.analytics-core.enabled to enable/disable GCS Analytics Core. The
> > >> current implementation always requires runtime dependency of GCS
> Analytics
> > >> Core even if the configuration is off. Ideally we can lazy load such
> > >> dependency so the dependency is only required when the feature is
> > >> explicitly enabled. But since GCP is likely to enable GCS Analytics
> Core by
> > >> default, I feel it's reasonable for downstream projects using
> non-bundle
> > >> jars to add this dependency.
> > >>
> > >>
> > >> On Thu, May 7, 2026 at 6:54 PM Steven Wu  wrote:
> > >>
> > >>> Looked a little more.
> > >>>
> > >>> So Iceberg's cloud modules consistently use compileOnly for vendor
> SDKs
> > >>> and rely on either the bundle artifact or downstream coordination for
> > >>> runtime. So, both changes are expected for downstream consumers
> using the
> > >>> non-bundle jars. Maybe we don't need to change anything.
> > >>>
> > >>> iceber

RE: Re: [VOTE] Release Apache Iceberg 1.11.0 RC1

[Ajay Yadav]

Hi Everyone,

I would like to report a performance regression we've identified in Spark 
queries on Iceberg tables stored in cloud storage (tested with GCS), which I 
believe should be addressed in the 1.11.0 release.

Current SerializableFileIOWithSize drops file length, causing performance 
regression due to excessive metadata calls in Cloud Storage: 
https://github.com/apache/iceberg/ssues/16283. The fix overrides InputFile 
newInputFile(String path, long length) to preserve file length and avoid 
unwanted metadata calls https://github.com/apache/iceberg/pull/16284


On 2026/05/08 15:27:05 Péter Váry wrote:
> Just to clarify:
> 
> The following PRs are already merged to 1.11.0:
> 
>- https://github.com/apache/iceberg/pull/14297 - Spark: Support writing
>shredded variant in Iceberg-Spark
>- https://github.com/apache/iceberg/pull/15512 - Spark: fix delete from
>branch for canDeleteWhere where it does not resolve to the correct branch -
>WAP fix
>- https://github.com/apache/iceberg/pull/15475 - Flink: Add Nanosecond
>Precision Support for Flink-Iceberg Integration
> 
> 
> The missing ones are the ones backporting those to other engine versions:
> 
>- For: 14297 :
>   - 16241  - Backport for
>   variant shredding in Spark 4.0
>- For: 15512 :
>   - 16245  - Spark:
>   backport PR #15512 to v3.4, v3.5, v4.0 for WAP branch delete fix
>- For: 15475 :
>   - #16183 ,  #16239
>   , #16240
>    - Backport for Nano
>   timestamps for Flink 2.0/1.20
> 
> 
> So the PRs needed on 1.11.0 are:
> https://github.com/apache/iceberg/pull/16241
> https://github.com/apache/iceberg/pull/16245
> https://github.com/apache/iceberg/pull/16183
> https://github.com/apache/iceberg/pull/16239
> https://github.com/apache/iceberg/pull/16240
> https://github.com/apache/iceberg/pull/16186
> 
> Aihua Xu  ezt írta (időpont: 2026. máj. 8., P, 17:13):
> 
> > Thank you all for the feedback and for verifying the release candidate.
> > Based on the issues identified above, we will include the following fixes
> > and cut RC2 with a new vote:
> >
> > https://github.com/apache/iceberg/pull/14297
> > https://github.com/apache/iceberg/pull/15512
> > https://github.com/apache/iceberg/pull/15475
> > https://github.com/apache/iceberg/pull/16186
> >
> > Please let me know if you have any questions or identified additional
> > issues.
> >
> > Thanks,
> > Aihua
> >
> > On Thu, May 7, 2026 at 10:09 PM Aihua Xu  wrote:
> >
> >> I also looked into this. There is a configuration
> >> gcs.analytics-core.enabled to enable/disable GCS Analytics Core. The
> >> current implementation always requires runtime dependency of GCS Analytics
> >> Core even if the configuration is off. Ideally we can lazy load such
> >> dependency so the dependency is only required when the feature is
> >> explicitly enabled. But since GCP is likely to enable GCS Analytics Core by
> >> default, I feel it's reasonable for downstream projects using non-bundle
> >> jars to add this dependency.
> >>
> >>
> >> On Thu, May 7, 2026 at 6:54 PM Steven Wu  wrote:
> >>
> >>> Looked a little more.
> >>>
> >>> So Iceberg's cloud modules consistently use compileOnly for vendor SDKs
> >>> and rely on either the bundle artifact or downstream coordination for
> >>> runtime. So, both changes are expected for downstream consumers using the
> >>> non-bundle jars. Maybe we don't need to change anything.
> >>>
> >>> iceberg-gcp module
> >>>
> >>> compileOnly platform(libs.google.libraries.bom)
> >>> compileOnly "com.google.cloud:google-cloud-storage"
> >>> compileOnly "com.google.cloud:google-cloud-kms"
> >>> compileOnly(libs.gcs.analytics.core)
> >>>
> >>>
> >>> On Thu, May 7, 2026 at 6:16 PM Steven Wu  wrote:
> >>>
>  Yuya, thanks for reporting the discovery.
> 
>  Azure: I approved your PR and can merge it soon:
>  https://github.com/apache/iceberg/pull/16186
>  GCP: the new dependency is marked as compileOnly in PR 14333
>  , as it is an opt-in
>  feature. we need to either change the dep to implementation or update the
>  code similar to the Azure fix above.
> 
> 
>  On Thu, May 7, 2026 at 4:07 PM Yuya Ebihara <
>  yuya.ebih...@starburstdata.com> wrote:
> 
> > Hi Aihua,
> >
> > Thanks for leading the release!
> >
> > Just a quick reminder about two dependency-related items from a
> > downstream perspective:
> > * Azure module users will require azure-security-keyvault-keys, even
> > when table encryption is not used, as noted in
> > https://git

Re: [VOTE] Release Apache Iceberg 1.11.0 RC1

[Talat Uyarer via dev]

Hi Everyone,

While testing my recent changes, we discovered a bug in the Iceberg Spark
code affecting queries. More detail about the bug:
https://github.com/apache/iceberg/issues/16283

Specifically, SerializableFileIOWithSize fails to override the
newInputFile(String path, long length) method. This oversight causes the
file length property to be dropped during Spark execution. We created a PR
to fix this bug: https://github.com/apache/iceberg/pull/16284

Talat


On Sat, May 9, 2026 at 5:43 PM Aihua Xu  wrote:

> Thanks for calling this out. This seems to be a blocker. I’ll pause and
> hold off on proceeding until it’s resolved.
>
>
> On Sat, May 9, 2026 at 10:03 AM Amogh Jahagirdar <2am...@gmail.com> wrote:
>
>> Hey folks, on our side we were looking at a customer issue yesterday and
>> observed that the first row IDs for existing entries weren't carried over
>> as expected when moving them to a new manifest. This violates the spec and
>> is naturally unexpected. I've published a draft
>>  with a minimal test
>> reproducing the issue and a possible fix, though I'm verifying that it's
>> the right fix. It would be good to get more eyes on this. Once we verify
>> it's a legitimate issue, I unfortunately think it's a release blocker
>> because it involves metadata corruption.
>>
>> Thanks,
>> Amogh Jahagirdar
>>
>> On Fri, May 8, 2026 at 3:31 PM Talat Uyarer  wrote:
>>
>>> Created a PR for this: https://github.com/apache/iceberg/pull/16258
>>>
>>> On 2026/05/08 20:04:04 Russell Spitzer wrote:
>>> > Just post here when you have it
>>> >
>>> > On Fri, May 8, 2026 at 3:03 PM Talat Uyarer  wrote:
>>> >
>>> > > I am working on a solution to decouple GCS and Analytic core if
>>> feature is
>>> > > not enabled. I will create a PR soon. But I need reviewer.
>>> > >
>>> > > On 2026/05/08 19:11:23 Kevin Liu wrote:
>>> > > > Looks like all the changes Peter linked above are now merged.
>>> > > >
>>> > > > I also merged the Azure PR (
>>> https://github.com/apache/iceberg/pull/16186
>>> > > ),
>>> > > > thanks for catching this.
>>> > > >
>>> > > > For the "GCS Analytics Core" issue, here's how I understand it:
>>> > > > - Users using `gcp-bundle` are fine, confirmed by Yuya in Trino,
>>> since
>>> > > the
>>> > > > bundle includes `gcs-analytics-core` in its shadow jar.
>>> > > > - Users using just `iceberg-gcp` (for GCSFileIO, etc.) will see
>>> > > > `NoClassDefFoundError` even though `gcs.analytics-core.enabled`
>>> defaults
>>> > > to
>>> > > > false.
>>> > > > *So `gcs-analytics-core` is a new required dependency to use
>>> GCSFileIO,
>>> > > > because analytics-core classes are eagerly loaded regardless of
>>> > > > configuration.*
>>> > > >
>>> > > > I also verified all 3 cloud bundles (AWS, Azure, GCP) for similar
>>> issues
>>> > > > and didn't find any additional cases.
>>> > > >
>>> > > > Best,
>>> > > > Kevin Liu
>>> > > >
>>> > > >
>>> > > > On Fri, May 8, 2026 at 11:15 AM Steve Loughran <
>>> ste...@cloudera.com>
>>> > > wrote:
>>> > > >
>>> > > > > I did actually get claude to do a packaging audit,
>>> > > > >
>>> > > > > verifying checksums, signatures, source code == tag *and* that
>>> the
>>> > > jars in
>>> > > > > nexus match those I get in a local build, i cover that process a
>>> bit
>>> > > more
>>> > > > > on the dev@parquet list for the curious; this one was just
>>> giving the
>>> > > > > claude session the new vote email and telling it to build with
>>> > > ./gradlew -x
>>> > > > > test -x integrationTest
>>> > > > >
>>> > > > > no problems there git source == .tar source ==> nexus artifacts
>>> > > > >
>>> > > > > On Fri, 8 May 2026 at 18:04, Steven Wu 
>>> wrote:
>>> > > > >
>>> > > > >> We will build RC2 from the latest main branch tonight.
>>> > > > >>
>>> > > > >> On Fri, May 8, 2026 at 8:27 AM Péter Váry <
>>> > > peter.vary.apa...@gmail.com>
>>> > > > >> wrote:
>>> > > > >>
>>> > > > >>> Just to clarify:
>>> > > > >>>
>>> > > > >>> The following PRs are already merged to 1.11.0:
>>> > > > >>>
>>> > > > >>>- https://github.com/apache/iceberg/pull/14297 - Spark:
>>> Support
>>> > > > >>>writing shredded variant in Iceberg-Spark
>>> > > > >>>- https://github.com/apache/iceberg/pull/15512 - Spark: fix
>>> > > delete
>>> > > > >>>from branch for canDeleteWhere where it does not resolve to
>>> the
>>> > > correct
>>> > > > >>>branch - WAP fix
>>> > > > >>>- https://github.com/apache/iceberg/pull/15475 - Flink: Add
>>> > > > >>>Nanosecond Precision Support for Flink-Iceberg Integration
>>> > > > >>>
>>> > > > >>>
>>> > > > >>> The missing ones are the ones backporting those to other engine
>>> > > versions:
>>> > > > >>>
>>> > > > >>>- For: 14297 >> >:
>>> > > > >>>   - 16241  -
>>> > > Backport
>>> > > > >>>   for variant shredding in Spark 4.0
>>> > > > >>>- For: 15512 

Re: [VOTE] Release Apache Iceberg 1.11.0 RC1

[Aihua Xu]

Thanks for calling this out. This seems to be a blocker. I’ll pause and
hold off on proceeding until it’s resolved.


On Sat, May 9, 2026 at 10:03 AM Amogh Jahagirdar <2am...@gmail.com> wrote:

> Hey folks, on our side we were looking at a customer issue yesterday and
> observed that the first row IDs for existing entries weren't carried over
> as expected when moving them to a new manifest. This violates the spec and
> is naturally unexpected. I've published a draft
>  with a minimal test
> reproducing the issue and a possible fix, though I'm verifying that it's
> the right fix. It would be good to get more eyes on this. Once we verify
> it's a legitimate issue, I unfortunately think it's a release blocker
> because it involves metadata corruption.
>
> Thanks,
> Amogh Jahagirdar
>
> On Fri, May 8, 2026 at 3:31 PM Talat Uyarer  wrote:
>
>> Created a PR for this: https://github.com/apache/iceberg/pull/16258
>>
>> On 2026/05/08 20:04:04 Russell Spitzer wrote:
>> > Just post here when you have it
>> >
>> > On Fri, May 8, 2026 at 3:03 PM Talat Uyarer  wrote:
>> >
>> > > I am working on a solution to decouple GCS and Analytic core if
>> feature is
>> > > not enabled. I will create a PR soon. But I need reviewer.
>> > >
>> > > On 2026/05/08 19:11:23 Kevin Liu wrote:
>> > > > Looks like all the changes Peter linked above are now merged.
>> > > >
>> > > > I also merged the Azure PR (
>> https://github.com/apache/iceberg/pull/16186
>> > > ),
>> > > > thanks for catching this.
>> > > >
>> > > > For the "GCS Analytics Core" issue, here's how I understand it:
>> > > > - Users using `gcp-bundle` are fine, confirmed by Yuya in Trino,
>> since
>> > > the
>> > > > bundle includes `gcs-analytics-core` in its shadow jar.
>> > > > - Users using just `iceberg-gcp` (for GCSFileIO, etc.) will see
>> > > > `NoClassDefFoundError` even though `gcs.analytics-core.enabled`
>> defaults
>> > > to
>> > > > false.
>> > > > *So `gcs-analytics-core` is a new required dependency to use
>> GCSFileIO,
>> > > > because analytics-core classes are eagerly loaded regardless of
>> > > > configuration.*
>> > > >
>> > > > I also verified all 3 cloud bundles (AWS, Azure, GCP) for similar
>> issues
>> > > > and didn't find any additional cases.
>> > > >
>> > > > Best,
>> > > > Kevin Liu
>> > > >
>> > > >
>> > > > On Fri, May 8, 2026 at 11:15 AM Steve Loughran > >
>> > > wrote:
>> > > >
>> > > > > I did actually get claude to do a packaging audit,
>> > > > >
>> > > > > verifying checksums, signatures, source code == tag *and* that the
>> > > jars in
>> > > > > nexus match those I get in a local build, i cover that process a
>> bit
>> > > more
>> > > > > on the dev@parquet list for the curious; this one was just
>> giving the
>> > > > > claude session the new vote email and telling it to build with
>> > > ./gradlew -x
>> > > > > test -x integrationTest
>> > > > >
>> > > > > no problems there git source == .tar source ==> nexus artifacts
>> > > > >
>> > > > > On Fri, 8 May 2026 at 18:04, Steven Wu 
>> wrote:
>> > > > >
>> > > > >> We will build RC2 from the latest main branch tonight.
>> > > > >>
>> > > > >> On Fri, May 8, 2026 at 8:27 AM Péter Váry <
>> > > peter.vary.apa...@gmail.com>
>> > > > >> wrote:
>> > > > >>
>> > > > >>> Just to clarify:
>> > > > >>>
>> > > > >>> The following PRs are already merged to 1.11.0:
>> > > > >>>
>> > > > >>>- https://github.com/apache/iceberg/pull/14297 - Spark:
>> Support
>> > > > >>>writing shredded variant in Iceberg-Spark
>> > > > >>>- https://github.com/apache/iceberg/pull/15512 - Spark: fix
>> > > delete
>> > > > >>>from branch for canDeleteWhere where it does not resolve to
>> the
>> > > correct
>> > > > >>>branch - WAP fix
>> > > > >>>- https://github.com/apache/iceberg/pull/15475 - Flink: Add
>> > > > >>>Nanosecond Precision Support for Flink-Iceberg Integration
>> > > > >>>
>> > > > >>>
>> > > > >>> The missing ones are the ones backporting those to other engine
>> > > versions:
>> > > > >>>
>> > > > >>>- For: 14297 :
>> > > > >>>   - 16241  -
>> > > Backport
>> > > > >>>   for variant shredding in Spark 4.0
>> > > > >>>- For: 15512 :
>> > > > >>>   - 16245  -
>> > > Spark:
>> > > > >>>   backport PR #15512 to v3.4, v3.5, v4.0 for WAP branch
>> delete
>> > > fix
>> > > > >>>- For: 15475 :
>> > > > >>>   - #16183 ,
>> > > #16239
>> > > > >>>   , #16240
>> > > > >>>    -
>> Backport for
>> > > > >>>   Nano timestamps for Flink 2.0/1.20
>> > > > >>>
>> > > > >>>
>> > > > >>> So the PRs needed on 1.11.0 are:
>> > > > >>> https://githu

Re: [VOTE] Release Apache Iceberg 1.11.0 RC1

[Amogh Jahagirdar]

Hey folks, on our side we were looking at a customer issue yesterday and
observed that the first row IDs for existing entries weren't carried over
as expected when moving them to a new manifest. This violates the spec and
is naturally unexpected. I've published a draft
 with a minimal test
reproducing the issue and a possible fix, though I'm verifying that it's
the right fix. It would be good to get more eyes on this. Once we verify
it's a legitimate issue, I unfortunately think it's a release blocker
because it involves metadata corruption.

Thanks,
Amogh Jahagirdar

On Fri, May 8, 2026 at 3:31 PM Talat Uyarer  wrote:

> Created a PR for this: https://github.com/apache/iceberg/pull/16258
>
> On 2026/05/08 20:04:04 Russell Spitzer wrote:
> > Just post here when you have it
> >
> > On Fri, May 8, 2026 at 3:03 PM Talat Uyarer  wrote:
> >
> > > I am working on a solution to decouple GCS and Analytic core if
> feature is
> > > not enabled. I will create a PR soon. But I need reviewer.
> > >
> > > On 2026/05/08 19:11:23 Kevin Liu wrote:
> > > > Looks like all the changes Peter linked above are now merged.
> > > >
> > > > I also merged the Azure PR (
> https://github.com/apache/iceberg/pull/16186
> > > ),
> > > > thanks for catching this.
> > > >
> > > > For the "GCS Analytics Core" issue, here's how I understand it:
> > > > - Users using `gcp-bundle` are fine, confirmed by Yuya in Trino,
> since
> > > the
> > > > bundle includes `gcs-analytics-core` in its shadow jar.
> > > > - Users using just `iceberg-gcp` (for GCSFileIO, etc.) will see
> > > > `NoClassDefFoundError` even though `gcs.analytics-core.enabled`
> defaults
> > > to
> > > > false.
> > > > *So `gcs-analytics-core` is a new required dependency to use
> GCSFileIO,
> > > > because analytics-core classes are eagerly loaded regardless of
> > > > configuration.*
> > > >
> > > > I also verified all 3 cloud bundles (AWS, Azure, GCP) for similar
> issues
> > > > and didn't find any additional cases.
> > > >
> > > > Best,
> > > > Kevin Liu
> > > >
> > > >
> > > > On Fri, May 8, 2026 at 11:15 AM Steve Loughran 
> > > wrote:
> > > >
> > > > > I did actually get claude to do a packaging audit,
> > > > >
> > > > > verifying checksums, signatures, source code == tag *and* that the
> > > jars in
> > > > > nexus match those I get in a local build, i cover that process a
> bit
> > > more
> > > > > on the dev@parquet list for the curious; this one was just giving
> the
> > > > > claude session the new vote email and telling it to build with
> > > ./gradlew -x
> > > > > test -x integrationTest
> > > > >
> > > > > no problems there git source == .tar source ==> nexus artifacts
> > > > >
> > > > > On Fri, 8 May 2026 at 18:04, Steven Wu 
> wrote:
> > > > >
> > > > >> We will build RC2 from the latest main branch tonight.
> > > > >>
> > > > >> On Fri, May 8, 2026 at 8:27 AM Péter Váry <
> > > peter.vary.apa...@gmail.com>
> > > > >> wrote:
> > > > >>
> > > > >>> Just to clarify:
> > > > >>>
> > > > >>> The following PRs are already merged to 1.11.0:
> > > > >>>
> > > > >>>- https://github.com/apache/iceberg/pull/14297 - Spark:
> Support
> > > > >>>writing shredded variant in Iceberg-Spark
> > > > >>>- https://github.com/apache/iceberg/pull/15512 - Spark: fix
> > > delete
> > > > >>>from branch for canDeleteWhere where it does not resolve to
> the
> > > correct
> > > > >>>branch - WAP fix
> > > > >>>- https://github.com/apache/iceberg/pull/15475 - Flink: Add
> > > > >>>Nanosecond Precision Support for Flink-Iceberg Integration
> > > > >>>
> > > > >>>
> > > > >>> The missing ones are the ones backporting those to other engine
> > > versions:
> > > > >>>
> > > > >>>- For: 14297 :
> > > > >>>   - 16241  -
> > > Backport
> > > > >>>   for variant shredding in Spark 4.0
> > > > >>>- For: 15512 :
> > > > >>>   - 16245  -
> > > Spark:
> > > > >>>   backport PR #15512 to v3.4, v3.5, v4.0 for WAP branch
> delete
> > > fix
> > > > >>>- For: 15475 :
> > > > >>>   - #16183 ,
> > > #16239
> > > > >>>   , #16240
> > > > >>>    - Backport
> for
> > > > >>>   Nano timestamps for Flink 2.0/1.20
> > > > >>>
> > > > >>>
> > > > >>> So the PRs needed on 1.11.0 are:
> > > > >>> https://github.com/apache/iceberg/pull/16241
> > > > >>> https://github.com/apache/iceberg/pull/16245
> > > > >>> https://github.com/apache/iceberg/pull/16183
> > > > >>> https://github.com/apache/iceberg/pull/16239
> > > > >>> https://github.com/apache/iceberg/pull/16240
> > > > >>> https://github.com/apache/iceberg/pull/16186
> > > > >>>
> > >

Re: [VOTE] Release Apache Iceberg 1.11.0 RC1

[Talat Uyarer]

Created a PR for this: https://github.com/apache/iceberg/pull/16258

On 2026/05/08 20:04:04 Russell Spitzer wrote:
> Just post here when you have it
> 
> On Fri, May 8, 2026 at 3:03 PM Talat Uyarer  wrote:
> 
> > I am working on a solution to decouple GCS and Analytic core if feature is
> > not enabled. I will create a PR soon. But I need reviewer.
> >
> > On 2026/05/08 19:11:23 Kevin Liu wrote:
> > > Looks like all the changes Peter linked above are now merged.
> > >
> > > I also merged the Azure PR (https://github.com/apache/iceberg/pull/16186
> > ),
> > > thanks for catching this.
> > >
> > > For the "GCS Analytics Core" issue, here's how I understand it:
> > > - Users using `gcp-bundle` are fine, confirmed by Yuya in Trino, since
> > the
> > > bundle includes `gcs-analytics-core` in its shadow jar.
> > > - Users using just `iceberg-gcp` (for GCSFileIO, etc.) will see
> > > `NoClassDefFoundError` even though `gcs.analytics-core.enabled` defaults
> > to
> > > false.
> > > *So `gcs-analytics-core` is a new required dependency to use GCSFileIO,
> > > because analytics-core classes are eagerly loaded regardless of
> > > configuration.*
> > >
> > > I also verified all 3 cloud bundles (AWS, Azure, GCP) for similar issues
> > > and didn't find any additional cases.
> > >
> > > Best,
> > > Kevin Liu
> > >
> > >
> > > On Fri, May 8, 2026 at 11:15 AM Steve Loughran 
> > wrote:
> > >
> > > > I did actually get claude to do a packaging audit,
> > > >
> > > > verifying checksums, signatures, source code == tag *and* that the
> > jars in
> > > > nexus match those I get in a local build, i cover that process a bit
> > more
> > > > on the dev@parquet list for the curious; this one was just giving the
> > > > claude session the new vote email and telling it to build with
> > ./gradlew -x
> > > > test -x integrationTest
> > > >
> > > > no problems there git source == .tar source ==> nexus artifacts
> > > >
> > > > On Fri, 8 May 2026 at 18:04, Steven Wu  wrote:
> > > >
> > > >> We will build RC2 from the latest main branch tonight.
> > > >>
> > > >> On Fri, May 8, 2026 at 8:27 AM Péter Váry <
> > peter.vary.apa...@gmail.com>
> > > >> wrote:
> > > >>
> > > >>> Just to clarify:
> > > >>>
> > > >>> The following PRs are already merged to 1.11.0:
> > > >>>
> > > >>>- https://github.com/apache/iceberg/pull/14297 - Spark: Support
> > > >>>writing shredded variant in Iceberg-Spark
> > > >>>- https://github.com/apache/iceberg/pull/15512 - Spark: fix
> > delete
> > > >>>from branch for canDeleteWhere where it does not resolve to the
> > correct
> > > >>>branch - WAP fix
> > > >>>- https://github.com/apache/iceberg/pull/15475 - Flink: Add
> > > >>>Nanosecond Precision Support for Flink-Iceberg Integration
> > > >>>
> > > >>>
> > > >>> The missing ones are the ones backporting those to other engine
> > versions:
> > > >>>
> > > >>>- For: 14297 :
> > > >>>   - 16241  -
> > Backport
> > > >>>   for variant shredding in Spark 4.0
> > > >>>- For: 15512 :
> > > >>>   - 16245  -
> > Spark:
> > > >>>   backport PR #15512 to v3.4, v3.5, v4.0 for WAP branch delete
> > fix
> > > >>>- For: 15475 :
> > > >>>   - #16183 ,
> > #16239
> > > >>>   , #16240
> > > >>>    - Backport for
> > > >>>   Nano timestamps for Flink 2.0/1.20
> > > >>>
> > > >>>
> > > >>> So the PRs needed on 1.11.0 are:
> > > >>> https://github.com/apache/iceberg/pull/16241
> > > >>> https://github.com/apache/iceberg/pull/16245
> > > >>> https://github.com/apache/iceberg/pull/16183
> > > >>> https://github.com/apache/iceberg/pull/16239
> > > >>> https://github.com/apache/iceberg/pull/16240
> > > >>> https://github.com/apache/iceberg/pull/16186
> > > >>>
> > > >>> Aihua Xu  ezt írta (időpont: 2026. máj. 8., P,
> > > >>> 17:13):
> > > >>>
> > >  Thank you all for the feedback and for verifying the release
> > candidate.
> > >  Based on the issues identified above, we will include the following
> > fixes
> > >  and cut RC2 with a new vote:
> > > 
> > >  https://github.com/apache/iceberg/pull/14297
> > >  https://github.com/apache/iceberg/pull/15512
> > >  https://github.com/apache/iceberg/pull/15475
> > >  https://github.com/apache/iceberg/pull/16186
> > > 
> > >  Please let me know if you have any questions or identified
> > additional
> > >  issues.
> > > 
> > >  Thanks,
> > >  Aihua
> > > 
> > >  On Thu, May 7, 2026 at 10:09 PM Aihua Xu  wrote:
> > > 
> > > > I also looked into this. There is a configuration
> > > > gcs.analytics-core.enabled to enable/disable GCS Analyt

Re: [VOTE] Release Apache Iceberg 1.11.0 RC1

[Russell Spitzer]

Just post here when you have it

On Fri, May 8, 2026 at 3:03 PM Talat Uyarer  wrote:

> I am working on a solution to decouple GCS and Analytic core if feature is
> not enabled. I will create a PR soon. But I need reviewer.
>
> On 2026/05/08 19:11:23 Kevin Liu wrote:
> > Looks like all the changes Peter linked above are now merged.
> >
> > I also merged the Azure PR (https://github.com/apache/iceberg/pull/16186
> ),
> > thanks for catching this.
> >
> > For the "GCS Analytics Core" issue, here's how I understand it:
> > - Users using `gcp-bundle` are fine, confirmed by Yuya in Trino, since
> the
> > bundle includes `gcs-analytics-core` in its shadow jar.
> > - Users using just `iceberg-gcp` (for GCSFileIO, etc.) will see
> > `NoClassDefFoundError` even though `gcs.analytics-core.enabled` defaults
> to
> > false.
> > *So `gcs-analytics-core` is a new required dependency to use GCSFileIO,
> > because analytics-core classes are eagerly loaded regardless of
> > configuration.*
> >
> > I also verified all 3 cloud bundles (AWS, Azure, GCP) for similar issues
> > and didn't find any additional cases.
> >
> > Best,
> > Kevin Liu
> >
> >
> > On Fri, May 8, 2026 at 11:15 AM Steve Loughran 
> wrote:
> >
> > > I did actually get claude to do a packaging audit,
> > >
> > > verifying checksums, signatures, source code == tag *and* that the
> jars in
> > > nexus match those I get in a local build, i cover that process a bit
> more
> > > on the dev@parquet list for the curious; this one was just giving the
> > > claude session the new vote email and telling it to build with
> ./gradlew -x
> > > test -x integrationTest
> > >
> > > no problems there git source == .tar source ==> nexus artifacts
> > >
> > > On Fri, 8 May 2026 at 18:04, Steven Wu  wrote:
> > >
> > >> We will build RC2 from the latest main branch tonight.
> > >>
> > >> On Fri, May 8, 2026 at 8:27 AM Péter Váry <
> peter.vary.apa...@gmail.com>
> > >> wrote:
> > >>
> > >>> Just to clarify:
> > >>>
> > >>> The following PRs are already merged to 1.11.0:
> > >>>
> > >>>- https://github.com/apache/iceberg/pull/14297 - Spark: Support
> > >>>writing shredded variant in Iceberg-Spark
> > >>>- https://github.com/apache/iceberg/pull/15512 - Spark: fix
> delete
> > >>>from branch for canDeleteWhere where it does not resolve to the
> correct
> > >>>branch - WAP fix
> > >>>- https://github.com/apache/iceberg/pull/15475 - Flink: Add
> > >>>Nanosecond Precision Support for Flink-Iceberg Integration
> > >>>
> > >>>
> > >>> The missing ones are the ones backporting those to other engine
> versions:
> > >>>
> > >>>- For: 14297 :
> > >>>   - 16241  -
> Backport
> > >>>   for variant shredding in Spark 4.0
> > >>>- For: 15512 :
> > >>>   - 16245  -
> Spark:
> > >>>   backport PR #15512 to v3.4, v3.5, v4.0 for WAP branch delete
> fix
> > >>>- For: 15475 :
> > >>>   - #16183 ,
> #16239
> > >>>   , #16240
> > >>>    - Backport for
> > >>>   Nano timestamps for Flink 2.0/1.20
> > >>>
> > >>>
> > >>> So the PRs needed on 1.11.0 are:
> > >>> https://github.com/apache/iceberg/pull/16241
> > >>> https://github.com/apache/iceberg/pull/16245
> > >>> https://github.com/apache/iceberg/pull/16183
> > >>> https://github.com/apache/iceberg/pull/16239
> > >>> https://github.com/apache/iceberg/pull/16240
> > >>> https://github.com/apache/iceberg/pull/16186
> > >>>
> > >>> Aihua Xu  ezt írta (időpont: 2026. máj. 8., P,
> > >>> 17:13):
> > >>>
> >  Thank you all for the feedback and for verifying the release
> candidate.
> >  Based on the issues identified above, we will include the following
> fixes
> >  and cut RC2 with a new vote:
> > 
> >  https://github.com/apache/iceberg/pull/14297
> >  https://github.com/apache/iceberg/pull/15512
> >  https://github.com/apache/iceberg/pull/15475
> >  https://github.com/apache/iceberg/pull/16186
> > 
> >  Please let me know if you have any questions or identified
> additional
> >  issues.
> > 
> >  Thanks,
> >  Aihua
> > 
> >  On Thu, May 7, 2026 at 10:09 PM Aihua Xu  wrote:
> > 
> > > I also looked into this. There is a configuration
> > > gcs.analytics-core.enabled to enable/disable GCS Analytics Core.
> The
> > > current implementation always requires runtime dependency of GCS
> Analytics
> > > Core even if the configuration is off. Ideally we can lazy load
> such
> > > dependency so the dependency is only required when the feature is
> > > explicitly enabled. But since GCP is likely to enable GCS
> Analytics Core by
> > > default

Re: [VOTE] Release Apache Iceberg 1.11.0 RC1

[Talat Uyarer]

I am working on a solution to decouple GCS and Analytic core if feature is not 
enabled. I will create a PR soon. But I need reviewer.

On 2026/05/08 19:11:23 Kevin Liu wrote:
> Looks like all the changes Peter linked above are now merged.
> 
> I also merged the Azure PR (https://github.com/apache/iceberg/pull/16186),
> thanks for catching this.
> 
> For the "GCS Analytics Core" issue, here's how I understand it:
> - Users using `gcp-bundle` are fine, confirmed by Yuya in Trino, since the
> bundle includes `gcs-analytics-core` in its shadow jar.
> - Users using just `iceberg-gcp` (for GCSFileIO, etc.) will see
> `NoClassDefFoundError` even though `gcs.analytics-core.enabled` defaults to
> false.
> *So `gcs-analytics-core` is a new required dependency to use GCSFileIO,
> because analytics-core classes are eagerly loaded regardless of
> configuration.*
> 
> I also verified all 3 cloud bundles (AWS, Azure, GCP) for similar issues
> and didn't find any additional cases.
> 
> Best,
> Kevin Liu
> 
> 
> On Fri, May 8, 2026 at 11:15 AM Steve Loughran  wrote:
> 
> > I did actually get claude to do a packaging audit,
> >
> > verifying checksums, signatures, source code == tag *and* that the jars in
> > nexus match those I get in a local build, i cover that process a bit more
> > on the dev@parquet list for the curious; this one was just giving the
> > claude session the new vote email and telling it to build with ./gradlew -x
> > test -x integrationTest
> >
> > no problems there git source == .tar source ==> nexus artifacts
> >
> > On Fri, 8 May 2026 at 18:04, Steven Wu  wrote:
> >
> >> We will build RC2 from the latest main branch tonight.
> >>
> >> On Fri, May 8, 2026 at 8:27 AM Péter Váry 
> >> wrote:
> >>
> >>> Just to clarify:
> >>>
> >>> The following PRs are already merged to 1.11.0:
> >>>
> >>>- https://github.com/apache/iceberg/pull/14297 - Spark: Support
> >>>writing shredded variant in Iceberg-Spark
> >>>- https://github.com/apache/iceberg/pull/15512 - Spark: fix delete
> >>>from branch for canDeleteWhere where it does not resolve to the correct
> >>>branch - WAP fix
> >>>- https://github.com/apache/iceberg/pull/15475 - Flink: Add
> >>>Nanosecond Precision Support for Flink-Iceberg Integration
> >>>
> >>>
> >>> The missing ones are the ones backporting those to other engine versions:
> >>>
> >>>- For: 14297 :
> >>>   - 16241  - Backport
> >>>   for variant shredding in Spark 4.0
> >>>- For: 15512 :
> >>>   - 16245  - Spark:
> >>>   backport PR #15512 to v3.4, v3.5, v4.0 for WAP branch delete fix
> >>>- For: 15475 :
> >>>   - #16183 ,  #16239
> >>>   , #16240
> >>>    - Backport for
> >>>   Nano timestamps for Flink 2.0/1.20
> >>>
> >>>
> >>> So the PRs needed on 1.11.0 are:
> >>> https://github.com/apache/iceberg/pull/16241
> >>> https://github.com/apache/iceberg/pull/16245
> >>> https://github.com/apache/iceberg/pull/16183
> >>> https://github.com/apache/iceberg/pull/16239
> >>> https://github.com/apache/iceberg/pull/16240
> >>> https://github.com/apache/iceberg/pull/16186
> >>>
> >>> Aihua Xu  ezt írta (időpont: 2026. máj. 8., P,
> >>> 17:13):
> >>>
>  Thank you all for the feedback and for verifying the release candidate.
>  Based on the issues identified above, we will include the following fixes
>  and cut RC2 with a new vote:
> 
>  https://github.com/apache/iceberg/pull/14297
>  https://github.com/apache/iceberg/pull/15512
>  https://github.com/apache/iceberg/pull/15475
>  https://github.com/apache/iceberg/pull/16186
> 
>  Please let me know if you have any questions or identified additional
>  issues.
> 
>  Thanks,
>  Aihua
> 
>  On Thu, May 7, 2026 at 10:09 PM Aihua Xu  wrote:
> 
> > I also looked into this. There is a configuration
> > gcs.analytics-core.enabled to enable/disable GCS Analytics Core. The
> > current implementation always requires runtime dependency of GCS 
> > Analytics
> > Core even if the configuration is off. Ideally we can lazy load such
> > dependency so the dependency is only required when the feature is
> > explicitly enabled. But since GCP is likely to enable GCS Analytics 
> > Core by
> > default, I feel it's reasonable for downstream projects using non-bundle
> > jars to add this dependency.
> >
> >
> > On Thu, May 7, 2026 at 6:54 PM Steven Wu  wrote:
> >
> >> Looked a little more.
> >>
> >> So Iceberg's cloud modules consistently use compileOnly for vendor
> >> SDKs and rely on either the bundle artif

Re: [VOTE] Release Apache Iceberg 1.11.0 RC1

[Kevin Liu]

Looks like all the changes Peter linked above are now merged.

I also merged the Azure PR (https://github.com/apache/iceberg/pull/16186),
thanks for catching this.

For the "GCS Analytics Core" issue, here's how I understand it:
- Users using `gcp-bundle` are fine, confirmed by Yuya in Trino, since the
bundle includes `gcs-analytics-core` in its shadow jar.
- Users using just `iceberg-gcp` (for GCSFileIO, etc.) will see
`NoClassDefFoundError` even though `gcs.analytics-core.enabled` defaults to
false.
*So `gcs-analytics-core` is a new required dependency to use GCSFileIO,
because analytics-core classes are eagerly loaded regardless of
configuration.*

I also verified all 3 cloud bundles (AWS, Azure, GCP) for similar issues
and didn't find any additional cases.

Best,
Kevin Liu


On Fri, May 8, 2026 at 11:15 AM Steve Loughran  wrote:

> I did actually get claude to do a packaging audit,
>
> verifying checksums, signatures, source code == tag *and* that the jars in
> nexus match those I get in a local build, i cover that process a bit more
> on the dev@parquet list for the curious; this one was just giving the
> claude session the new vote email and telling it to build with ./gradlew -x
> test -x integrationTest
>
> no problems there git source == .tar source ==> nexus artifacts
>
> On Fri, 8 May 2026 at 18:04, Steven Wu  wrote:
>
>> We will build RC2 from the latest main branch tonight.
>>
>> On Fri, May 8, 2026 at 8:27 AM Péter Váry 
>> wrote:
>>
>>> Just to clarify:
>>>
>>> The following PRs are already merged to 1.11.0:
>>>
>>>- https://github.com/apache/iceberg/pull/14297 - Spark: Support
>>>writing shredded variant in Iceberg-Spark
>>>- https://github.com/apache/iceberg/pull/15512 - Spark: fix delete
>>>from branch for canDeleteWhere where it does not resolve to the correct
>>>branch - WAP fix
>>>- https://github.com/apache/iceberg/pull/15475 - Flink: Add
>>>Nanosecond Precision Support for Flink-Iceberg Integration
>>>
>>>
>>> The missing ones are the ones backporting those to other engine versions:
>>>
>>>- For: 14297 :
>>>   - 16241  - Backport
>>>   for variant shredding in Spark 4.0
>>>- For: 15512 :
>>>   - 16245  - Spark:
>>>   backport PR #15512 to v3.4, v3.5, v4.0 for WAP branch delete fix
>>>- For: 15475 :
>>>   - #16183 ,  #16239
>>>   , #16240
>>>    - Backport for
>>>   Nano timestamps for Flink 2.0/1.20
>>>
>>>
>>> So the PRs needed on 1.11.0 are:
>>> https://github.com/apache/iceberg/pull/16241
>>> https://github.com/apache/iceberg/pull/16245
>>> https://github.com/apache/iceberg/pull/16183
>>> https://github.com/apache/iceberg/pull/16239
>>> https://github.com/apache/iceberg/pull/16240
>>> https://github.com/apache/iceberg/pull/16186
>>>
>>> Aihua Xu  ezt írta (időpont: 2026. máj. 8., P,
>>> 17:13):
>>>
 Thank you all for the feedback and for verifying the release candidate.
 Based on the issues identified above, we will include the following fixes
 and cut RC2 with a new vote:

 https://github.com/apache/iceberg/pull/14297
 https://github.com/apache/iceberg/pull/15512
 https://github.com/apache/iceberg/pull/15475
 https://github.com/apache/iceberg/pull/16186

 Please let me know if you have any questions or identified additional
 issues.

 Thanks,
 Aihua

 On Thu, May 7, 2026 at 10:09 PM Aihua Xu  wrote:

> I also looked into this. There is a configuration
> gcs.analytics-core.enabled to enable/disable GCS Analytics Core. The
> current implementation always requires runtime dependency of GCS Analytics
> Core even if the configuration is off. Ideally we can lazy load such
> dependency so the dependency is only required when the feature is
> explicitly enabled. But since GCP is likely to enable GCS Analytics Core 
> by
> default, I feel it's reasonable for downstream projects using non-bundle
> jars to add this dependency.
>
>
> On Thu, May 7, 2026 at 6:54 PM Steven Wu  wrote:
>
>> Looked a little more.
>>
>> So Iceberg's cloud modules consistently use compileOnly for vendor
>> SDKs and rely on either the bundle artifact or downstream coordination 
>> for
>> runtime. So, both changes are expected for downstream consumers using the
>> non-bundle jars. Maybe we don't need to change anything.
>>
>> iceberg-gcp module
>>
>> compileOnly platform(libs.google.libraries.bom)
>> compileOnly "com.google.cloud:google-cloud-storage"
>> compileOnly "com.google.cloud:google-cloud-kms"
>> compileOn

Re: [VOTE] Release Apache Iceberg 1.11.0 RC1

[Steve Loughran]

I did actually get claude to do a packaging audit,

verifying checksums, signatures, source code == tag *and* that the jars in
nexus match those I get in a local build, i cover that process a bit more
on the dev@parquet list for the curious; this one was just giving the
claude session the new vote email and telling it to build with ./gradlew -x
test -x integrationTest

no problems there git source == .tar source ==> nexus artifacts

On Fri, 8 May 2026 at 18:04, Steven Wu  wrote:

> We will build RC2 from the latest main branch tonight.
>
> On Fri, May 8, 2026 at 8:27 AM Péter Váry 
> wrote:
>
>> Just to clarify:
>>
>> The following PRs are already merged to 1.11.0:
>>
>>- https://github.com/apache/iceberg/pull/14297 - Spark: Support
>>writing shredded variant in Iceberg-Spark
>>- https://github.com/apache/iceberg/pull/15512 - Spark: fix delete
>>from branch for canDeleteWhere where it does not resolve to the correct
>>branch - WAP fix
>>- https://github.com/apache/iceberg/pull/15475 - Flink: Add
>>Nanosecond Precision Support for Flink-Iceberg Integration
>>
>>
>> The missing ones are the ones backporting those to other engine versions:
>>
>>- For: 14297 :
>>   - 16241  - Backport
>>   for variant shredding in Spark 4.0
>>- For: 15512 :
>>   - 16245  - Spark:
>>   backport PR #15512 to v3.4, v3.5, v4.0 for WAP branch delete fix
>>- For: 15475 :
>>   - #16183 ,  #16239
>>   , #16240
>>    - Backport for Nano
>>   timestamps for Flink 2.0/1.20
>>
>>
>> So the PRs needed on 1.11.0 are:
>> https://github.com/apache/iceberg/pull/16241
>> https://github.com/apache/iceberg/pull/16245
>> https://github.com/apache/iceberg/pull/16183
>> https://github.com/apache/iceberg/pull/16239
>> https://github.com/apache/iceberg/pull/16240
>> https://github.com/apache/iceberg/pull/16186
>>
>> Aihua Xu  ezt írta (időpont: 2026. máj. 8., P, 17:13):
>>
>>> Thank you all for the feedback and for verifying the release candidate.
>>> Based on the issues identified above, we will include the following fixes
>>> and cut RC2 with a new vote:
>>>
>>> https://github.com/apache/iceberg/pull/14297
>>> https://github.com/apache/iceberg/pull/15512
>>> https://github.com/apache/iceberg/pull/15475
>>> https://github.com/apache/iceberg/pull/16186
>>>
>>> Please let me know if you have any questions or identified additional
>>> issues.
>>>
>>> Thanks,
>>> Aihua
>>>
>>> On Thu, May 7, 2026 at 10:09 PM Aihua Xu  wrote:
>>>
 I also looked into this. There is a configuration
 gcs.analytics-core.enabled to enable/disable GCS Analytics Core. The
 current implementation always requires runtime dependency of GCS Analytics
 Core even if the configuration is off. Ideally we can lazy load such
 dependency so the dependency is only required when the feature is
 explicitly enabled. But since GCP is likely to enable GCS Analytics Core by
 default, I feel it's reasonable for downstream projects using non-bundle
 jars to add this dependency.


 On Thu, May 7, 2026 at 6:54 PM Steven Wu  wrote:

> Looked a little more.
>
> So Iceberg's cloud modules consistently use compileOnly for vendor
> SDKs and rely on either the bundle artifact or downstream coordination for
> runtime. So, both changes are expected for downstream consumers using the
> non-bundle jars. Maybe we don't need to change anything.
>
> iceberg-gcp module
>
> compileOnly platform(libs.google.libraries.bom)
> compileOnly "com.google.cloud:google-cloud-storage"
> compileOnly "com.google.cloud:google-cloud-kms"
> compileOnly(libs.gcs.analytics.core)
>
>
> On Thu, May 7, 2026 at 6:16 PM Steven Wu  wrote:
>
>> Yuya, thanks for reporting the discovery.
>>
>> Azure: I approved your PR and can merge it soon:
>> https://github.com/apache/iceberg/pull/16186
>> GCP: the new dependency is marked as compileOnly in PR 14333
>> , as it is an opt-in
>> feature. we need to either change the dep to implementation or update the
>> code similar to the Azure fix above.
>>
>>
>> On Thu, May 7, 2026 at 4:07 PM Yuya Ebihara <
>> yuya.ebih...@starburstdata.com> wrote:
>>
>>> Hi Aihua,
>>>
>>> Thanks for leading the release!
>>>
>>> Just a quick reminder about two dependency-related items from a
>>> downstream perspective:
>>> * Azure module users will require azure-security-keyvault-keys, even
>>> when table encryption is not used, as noted in
>>> 

Re: [VOTE] Release Apache Iceberg 1.11.0 RC1

[Steven Wu]

We will build RC2 from the latest main branch tonight.

On Fri, May 8, 2026 at 8:27 AM Péter Váry 
wrote:

> Just to clarify:
>
> The following PRs are already merged to 1.11.0:
>
>- https://github.com/apache/iceberg/pull/14297 - Spark: Support
>writing shredded variant in Iceberg-Spark
>- https://github.com/apache/iceberg/pull/15512 - Spark: fix delete
>from branch for canDeleteWhere where it does not resolve to the correct
>branch - WAP fix
>- https://github.com/apache/iceberg/pull/15475 - Flink: Add Nanosecond
>Precision Support for Flink-Iceberg Integration
>
>
> The missing ones are the ones backporting those to other engine versions:
>
>- For: 14297 :
>   - 16241  - Backport
>   for variant shredding in Spark 4.0
>- For: 15512 :
>   - 16245  - Spark:
>   backport PR #15512 to v3.4, v3.5, v4.0 for WAP branch delete fix
>- For: 15475 :
>   - #16183 ,  #16239
>   , #16240
>    - Backport for Nano
>   timestamps for Flink 2.0/1.20
>
>
> So the PRs needed on 1.11.0 are:
> https://github.com/apache/iceberg/pull/16241
> https://github.com/apache/iceberg/pull/16245
> https://github.com/apache/iceberg/pull/16183
> https://github.com/apache/iceberg/pull/16239
> https://github.com/apache/iceberg/pull/16240
> https://github.com/apache/iceberg/pull/16186
>
> Aihua Xu  ezt írta (időpont: 2026. máj. 8., P, 17:13):
>
>> Thank you all for the feedback and for verifying the release candidate.
>> Based on the issues identified above, we will include the following fixes
>> and cut RC2 with a new vote:
>>
>> https://github.com/apache/iceberg/pull/14297
>> https://github.com/apache/iceberg/pull/15512
>> https://github.com/apache/iceberg/pull/15475
>> https://github.com/apache/iceberg/pull/16186
>>
>> Please let me know if you have any questions or identified additional
>> issues.
>>
>> Thanks,
>> Aihua
>>
>> On Thu, May 7, 2026 at 10:09 PM Aihua Xu  wrote:
>>
>>> I also looked into this. There is a configuration
>>> gcs.analytics-core.enabled to enable/disable GCS Analytics Core. The
>>> current implementation always requires runtime dependency of GCS Analytics
>>> Core even if the configuration is off. Ideally we can lazy load such
>>> dependency so the dependency is only required when the feature is
>>> explicitly enabled. But since GCP is likely to enable GCS Analytics Core by
>>> default, I feel it's reasonable for downstream projects using non-bundle
>>> jars to add this dependency.
>>>
>>>
>>> On Thu, May 7, 2026 at 6:54 PM Steven Wu  wrote:
>>>
 Looked a little more.

 So Iceberg's cloud modules consistently use compileOnly for vendor SDKs
 and rely on either the bundle artifact or downstream coordination for
 runtime. So, both changes are expected for downstream consumers using the
 non-bundle jars. Maybe we don't need to change anything.

 iceberg-gcp module

 compileOnly platform(libs.google.libraries.bom)
 compileOnly "com.google.cloud:google-cloud-storage"
 compileOnly "com.google.cloud:google-cloud-kms"
 compileOnly(libs.gcs.analytics.core)


 On Thu, May 7, 2026 at 6:16 PM Steven Wu  wrote:

> Yuya, thanks for reporting the discovery.
>
> Azure: I approved your PR and can merge it soon:
> https://github.com/apache/iceberg/pull/16186
> GCP: the new dependency is marked as compileOnly in PR 14333
> , as it is an opt-in
> feature. we need to either change the dep to implementation or update the
> code similar to the Azure fix above.
>
>
> On Thu, May 7, 2026 at 4:07 PM Yuya Ebihara <
> yuya.ebih...@starburstdata.com> wrote:
>
>> Hi Aihua,
>>
>> Thanks for leading the release!
>>
>> Just a quick reminder about two dependency-related items from a
>> downstream perspective:
>> * Azure module users will require azure-security-keyvault-keys, even
>> when table encryption is not used, as noted in
>> https://github.com/apache/iceberg/pull/16186
>> * GCS module users will require gcs-analytics-core
>>
>> I ran into CI failures with 1.11.0 in Trino because the project does
>> not use the azure-bundle or gcp-bundle modules.
>> The CI passed once we explicitly added these two dependencies.
>>
>> Thanks,
>> Yuya Ebihara
>>
>> On Fri, May 8, 2026 at 4:58 AM Péter Váry <
>> peter.vary.apa...@gmail.com> wrote:
>>
>>> First of all, thanks to everyone for the effort put into preparing
>>> this release!
>>>
>>> I would like to highlight

Re: [VOTE] Release Apache Iceberg 1.11.0 RC1

[Péter Váry]

Just to clarify:

The following PRs are already merged to 1.11.0:

   - https://github.com/apache/iceberg/pull/14297 - Spark: Support writing
   shredded variant in Iceberg-Spark
   - https://github.com/apache/iceberg/pull/15512 - Spark: fix delete from
   branch for canDeleteWhere where it does not resolve to the correct branch -
   WAP fix
   - https://github.com/apache/iceberg/pull/15475 - Flink: Add Nanosecond
   Precision Support for Flink-Iceberg Integration


The missing ones are the ones backporting those to other engine versions:

   - For: 14297 :
  - 16241  - Backport for
  variant shredding in Spark 4.0
   - For: 15512 :
  - 16245  - Spark:
  backport PR #15512 to v3.4, v3.5, v4.0 for WAP branch delete fix
   - For: 15475 :
  - #16183 ,  #16239
  , #16240
   - Backport for Nano
  timestamps for Flink 2.0/1.20


So the PRs needed on 1.11.0 are:
https://github.com/apache/iceberg/pull/16241
https://github.com/apache/iceberg/pull/16245
https://github.com/apache/iceberg/pull/16183
https://github.com/apache/iceberg/pull/16239
https://github.com/apache/iceberg/pull/16240
https://github.com/apache/iceberg/pull/16186

Aihua Xu  ezt írta (időpont: 2026. máj. 8., P, 17:13):

> Thank you all for the feedback and for verifying the release candidate.
> Based on the issues identified above, we will include the following fixes
> and cut RC2 with a new vote:
>
> https://github.com/apache/iceberg/pull/14297
> https://github.com/apache/iceberg/pull/15512
> https://github.com/apache/iceberg/pull/15475
> https://github.com/apache/iceberg/pull/16186
>
> Please let me know if you have any questions or identified additional
> issues.
>
> Thanks,
> Aihua
>
> On Thu, May 7, 2026 at 10:09 PM Aihua Xu  wrote:
>
>> I also looked into this. There is a configuration
>> gcs.analytics-core.enabled to enable/disable GCS Analytics Core. The
>> current implementation always requires runtime dependency of GCS Analytics
>> Core even if the configuration is off. Ideally we can lazy load such
>> dependency so the dependency is only required when the feature is
>> explicitly enabled. But since GCP is likely to enable GCS Analytics Core by
>> default, I feel it's reasonable for downstream projects using non-bundle
>> jars to add this dependency.
>>
>>
>> On Thu, May 7, 2026 at 6:54 PM Steven Wu  wrote:
>>
>>> Looked a little more.
>>>
>>> So Iceberg's cloud modules consistently use compileOnly for vendor SDKs
>>> and rely on either the bundle artifact or downstream coordination for
>>> runtime. So, both changes are expected for downstream consumers using the
>>> non-bundle jars. Maybe we don't need to change anything.
>>>
>>> iceberg-gcp module
>>>
>>> compileOnly platform(libs.google.libraries.bom)
>>> compileOnly "com.google.cloud:google-cloud-storage"
>>> compileOnly "com.google.cloud:google-cloud-kms"
>>> compileOnly(libs.gcs.analytics.core)
>>>
>>>
>>> On Thu, May 7, 2026 at 6:16 PM Steven Wu  wrote:
>>>
 Yuya, thanks for reporting the discovery.

 Azure: I approved your PR and can merge it soon:
 https://github.com/apache/iceberg/pull/16186
 GCP: the new dependency is marked as compileOnly in PR 14333
 , as it is an opt-in
 feature. we need to either change the dep to implementation or update the
 code similar to the Azure fix above.


 On Thu, May 7, 2026 at 4:07 PM Yuya Ebihara <
 yuya.ebih...@starburstdata.com> wrote:

> Hi Aihua,
>
> Thanks for leading the release!
>
> Just a quick reminder about two dependency-related items from a
> downstream perspective:
> * Azure module users will require azure-security-keyvault-keys, even
> when table encryption is not used, as noted in
> https://github.com/apache/iceberg/pull/16186
> * GCS module users will require gcs-analytics-core
>
> I ran into CI failures with 1.11.0 in Trino because the project does
> not use the azure-bundle or gcp-bundle modules.
> The CI passed once we explicitly added these two dependencies.
>
> Thanks,
> Yuya Ebihara
>
> On Fri, May 8, 2026 at 4:58 AM Péter Váry 
> wrote:
>
>> First of all, thanks to everyone for the effort put into preparing
>> this release!
>>
>> I would like to highlight that RC1 is built from a branch where the
>> following features have not been backported to all engine versions:
>> - Spark: Support writing shredded variant in Iceberg-Spark (
>> https://github.com/apache/iceberg/pull/14297) - Available in Spark
>> 4.1, but not in Spark

Re: [VOTE] Release Apache Iceberg 1.11.0 RC1

[Aihua Xu]

Thank you all for the feedback and for verifying the release candidate.
Based on the issues identified above, we will include the following fixes
and cut RC2 with a new vote:

https://github.com/apache/iceberg/pull/14297
https://github.com/apache/iceberg/pull/15512
https://github.com/apache/iceberg/pull/15475
https://github.com/apache/iceberg/pull/16186

Please let me know if you have any questions or identified additional
issues.

Thanks,
Aihua

On Thu, May 7, 2026 at 10:09 PM Aihua Xu  wrote:

> I also looked into this. There is a configuration
> gcs.analytics-core.enabled to enable/disable GCS Analytics Core. The
> current implementation always requires runtime dependency of GCS Analytics
> Core even if the configuration is off. Ideally we can lazy load such
> dependency so the dependency is only required when the feature is
> explicitly enabled. But since GCP is likely to enable GCS Analytics Core by
> default, I feel it's reasonable for downstream projects using non-bundle
> jars to add this dependency.
>
>
> On Thu, May 7, 2026 at 6:54 PM Steven Wu  wrote:
>
>> Looked a little more.
>>
>> So Iceberg's cloud modules consistently use compileOnly for vendor SDKs
>> and rely on either the bundle artifact or downstream coordination for
>> runtime. So, both changes are expected for downstream consumers using the
>> non-bundle jars. Maybe we don't need to change anything.
>>
>> iceberg-gcp module
>>
>> compileOnly platform(libs.google.libraries.bom)
>> compileOnly "com.google.cloud:google-cloud-storage"
>> compileOnly "com.google.cloud:google-cloud-kms"
>> compileOnly(libs.gcs.analytics.core)
>>
>>
>> On Thu, May 7, 2026 at 6:16 PM Steven Wu  wrote:
>>
>>> Yuya, thanks for reporting the discovery.
>>>
>>> Azure: I approved your PR and can merge it soon:
>>> https://github.com/apache/iceberg/pull/16186
>>> GCP: the new dependency is marked as compileOnly in PR 14333
>>> , as it is an opt-in
>>> feature. we need to either change the dep to implementation or update the
>>> code similar to the Azure fix above.
>>>
>>>
>>> On Thu, May 7, 2026 at 4:07 PM Yuya Ebihara <
>>> yuya.ebih...@starburstdata.com> wrote:
>>>
 Hi Aihua,

 Thanks for leading the release!

 Just a quick reminder about two dependency-related items from a
 downstream perspective:
 * Azure module users will require azure-security-keyvault-keys, even
 when table encryption is not used, as noted in
 https://github.com/apache/iceberg/pull/16186
 * GCS module users will require gcs-analytics-core

 I ran into CI failures with 1.11.0 in Trino because the project does
 not use the azure-bundle or gcp-bundle modules.
 The CI passed once we explicitly added these two dependencies.

 Thanks,
 Yuya Ebihara

 On Fri, May 8, 2026 at 4:58 AM Péter Váry 
 wrote:

> First of all, thanks to everyone for the effort put into preparing
> this release!
>
> I would like to highlight that RC1 is built from a branch where the
> following features have not been backported to all engine versions:
> - Spark: Support writing shredded variant in Iceberg-Spark (
> https://github.com/apache/iceberg/pull/14297) - Available in Spark
> 4.1, but not in Spark 4.0
> - Spark: fix delete from branch for canDeleteWhere where it does not
> resolve to the correct branch (
> https://github.com/apache/iceberg/pull/15512) - Available in Spark
> 4.1, but not in Spark 4.0, 3.5, or 3.4
> - Flink: Add Nanosecond Precision Support for Flink-Iceberg
> Integration (https://github.com/apache/iceberg/pull/15475) -
> Available in Flink 2.1, but not in Flink 2.0 or 1.20
>
> It is up to the community to decide whether these missing backports
> should be considered release blockers. Most of the corresponding PRs have
> already been merged to main (except #15512), and including them in the
> release should be relatively straightforward.
>
> From my perspective, I would prefer not to release with these gaps.
> That said, I understand the urgency and the need for a release, and I am
> happy to go with the community’s decision.
>
> Peter
>
> Aihua Xu  ezt írta (időpont: 2026. máj. 7., Cs,
> 18:26):
>
>> Hi Everyone,
>>
>> I propose that we release the following RC as the official Apache
>> Iceberg 1.11.0 release.
>>
>> The commit ID is 0f657edf12dc29f8487a679bfdd4210e9588d014
>> * This corresponds to the tag: apache-iceberg-1.11.0-rc1
>> * https://github.com/apache/iceberg/commits/apache-iceberg-1.11.0-rc1
>> *
>> https://github.com/apache/iceberg/tree/0f657edf12dc29f8487a679bfdd4210e9588d014
>>
>> The release tarball, signature, and checksums are here:
>> *
>> https://dist.apache.org/repos/dist/dev/iceberg/apache-iceberg-1.11.0-rc1
>>
>> You can find the KEYS file here:
>> * https://downloads

Re: [VOTE] Release Apache Iceberg 1.11.0 RC1

[Aihua Xu]

I also looked into this. There is a configuration gcs.analytics-core.enabled to
enable/disable GCS Analytics Core. The current implementation always
requires runtime dependency of GCS Analytics Core even if the configuration
is off. Ideally we can lazy load such dependency so the dependency is only
required when the feature is explicitly enabled. But since GCP is likely to
enable GCS Analytics Core by default, I feel it's reasonable for downstream
projects using non-bundle jars to add this dependency.


On Thu, May 7, 2026 at 6:54 PM Steven Wu  wrote:

> Looked a little more.
>
> So Iceberg's cloud modules consistently use compileOnly for vendor SDKs
> and rely on either the bundle artifact or downstream coordination for
> runtime. So, both changes are expected for downstream consumers using the
> non-bundle jars. Maybe we don't need to change anything.
>
> iceberg-gcp module
>
> compileOnly platform(libs.google.libraries.bom)
> compileOnly "com.google.cloud:google-cloud-storage"
> compileOnly "com.google.cloud:google-cloud-kms"
> compileOnly(libs.gcs.analytics.core)
>
>
> On Thu, May 7, 2026 at 6:16 PM Steven Wu  wrote:
>
>> Yuya, thanks for reporting the discovery.
>>
>> Azure: I approved your PR and can merge it soon:
>> https://github.com/apache/iceberg/pull/16186
>> GCP: the new dependency is marked as compileOnly in PR 14333
>> , as it is an opt-in
>> feature. we need to either change the dep to implementation or update the
>> code similar to the Azure fix above.
>>
>>
>> On Thu, May 7, 2026 at 4:07 PM Yuya Ebihara <
>> yuya.ebih...@starburstdata.com> wrote:
>>
>>> Hi Aihua,
>>>
>>> Thanks for leading the release!
>>>
>>> Just a quick reminder about two dependency-related items from a
>>> downstream perspective:
>>> * Azure module users will require azure-security-keyvault-keys, even
>>> when table encryption is not used, as noted in
>>> https://github.com/apache/iceberg/pull/16186
>>> * GCS module users will require gcs-analytics-core
>>>
>>> I ran into CI failures with 1.11.0 in Trino because the project does not
>>> use the azure-bundle or gcp-bundle modules.
>>> The CI passed once we explicitly added these two dependencies.
>>>
>>> Thanks,
>>> Yuya Ebihara
>>>
>>> On Fri, May 8, 2026 at 4:58 AM Péter Váry 
>>> wrote:
>>>
 First of all, thanks to everyone for the effort put into preparing this
 release!

 I would like to highlight that RC1 is built from a branch where the
 following features have not been backported to all engine versions:
 - Spark: Support writing shredded variant in Iceberg-Spark (
 https://github.com/apache/iceberg/pull/14297) - Available in Spark
 4.1, but not in Spark 4.0
 - Spark: fix delete from branch for canDeleteWhere where it does not
 resolve to the correct branch (
 https://github.com/apache/iceberg/pull/15512) - Available in Spark
 4.1, but not in Spark 4.0, 3.5, or 3.4
 - Flink: Add Nanosecond Precision Support for Flink-Iceberg Integration
 (https://github.com/apache/iceberg/pull/15475) - Available in Flink
 2.1, but not in Flink 2.0 or 1.20

 It is up to the community to decide whether these missing backports
 should be considered release blockers. Most of the corresponding PRs have
 already been merged to main (except #15512), and including them in the
 release should be relatively straightforward.

 From my perspective, I would prefer not to release with these gaps.
 That said, I understand the urgency and the need for a release, and I am
 happy to go with the community’s decision.

 Peter

 Aihua Xu  ezt írta (időpont: 2026. máj. 7., Cs,
 18:26):

> Hi Everyone,
>
> I propose that we release the following RC as the official Apache
> Iceberg 1.11.0 release.
>
> The commit ID is 0f657edf12dc29f8487a679bfdd4210e9588d014
> * This corresponds to the tag: apache-iceberg-1.11.0-rc1
> * https://github.com/apache/iceberg/commits/apache-iceberg-1.11.0-rc1
> *
> https://github.com/apache/iceberg/tree/0f657edf12dc29f8487a679bfdd4210e9588d014
>
> The release tarball, signature, and checksums are here:
> *
> https://dist.apache.org/repos/dist/dev/iceberg/apache-iceberg-1.11.0-rc1
>
> You can find the KEYS file here:
> * https://downloads.apache.org/iceberg/KEYS
>
> Convenience binary artifacts are staged on Nexus. The Maven repository
> URL is:
> *
> https://repository.apache.org/content/repositories/orgapacheiceberg-1278/
>
> Please download, verify, and test.
>
> Instructions for verifying a release can be found here:
> * https://iceberg.apache.org/how-to-release/#how-to-verify-a-release
>
> Please vote in the next 72 hours.
>
> [ ] +1 Release this as Apache Iceberg 1.11.0
> [ ] +0
> [ ] -1 Do not release this because...
>
> Only PMC members have binding votes, but other c

Re: [VOTE] Release Apache Iceberg 1.11.0 RC1

[Steven Wu]

Looked a little more.

So Iceberg's cloud modules consistently use compileOnly for vendor SDKs and
rely on either the bundle artifact or downstream coordination for runtime.
So, both changes are expected for downstream consumers using the non-bundle
jars. Maybe we don't need to change anything.

iceberg-gcp module

compileOnly platform(libs.google.libraries.bom)
compileOnly "com.google.cloud:google-cloud-storage"
compileOnly "com.google.cloud:google-cloud-kms"
compileOnly(libs.gcs.analytics.core)


On Thu, May 7, 2026 at 6:16 PM Steven Wu  wrote:

> Yuya, thanks for reporting the discovery.
>
> Azure: I approved your PR and can merge it soon:
> https://github.com/apache/iceberg/pull/16186
> GCP: the new dependency is marked as compileOnly in PR 14333
> , as it is an opt-in
> feature. we need to either change the dep to implementation or update the
> code similar to the Azure fix above.
>
>
> On Thu, May 7, 2026 at 4:07 PM Yuya Ebihara <
> yuya.ebih...@starburstdata.com> wrote:
>
>> Hi Aihua,
>>
>> Thanks for leading the release!
>>
>> Just a quick reminder about two dependency-related items from a
>> downstream perspective:
>> * Azure module users will require azure-security-keyvault-keys, even when
>> table encryption is not used, as noted in
>> https://github.com/apache/iceberg/pull/16186
>> * GCS module users will require gcs-analytics-core
>>
>> I ran into CI failures with 1.11.0 in Trino because the project does not
>> use the azure-bundle or gcp-bundle modules.
>> The CI passed once we explicitly added these two dependencies.
>>
>> Thanks,
>> Yuya Ebihara
>>
>> On Fri, May 8, 2026 at 4:58 AM Péter Váry 
>> wrote:
>>
>>> First of all, thanks to everyone for the effort put into preparing this
>>> release!
>>>
>>> I would like to highlight that RC1 is built from a branch where the
>>> following features have not been backported to all engine versions:
>>> - Spark: Support writing shredded variant in Iceberg-Spark (
>>> https://github.com/apache/iceberg/pull/14297) - Available in Spark 4.1,
>>> but not in Spark 4.0
>>> - Spark: fix delete from branch for canDeleteWhere where it does not
>>> resolve to the correct branch (
>>> https://github.com/apache/iceberg/pull/15512) - Available in Spark 4.1,
>>> but not in Spark 4.0, 3.5, or 3.4
>>> - Flink: Add Nanosecond Precision Support for Flink-Iceberg Integration (
>>> https://github.com/apache/iceberg/pull/15475) - Available in Flink 2.1,
>>> but not in Flink 2.0 or 1.20
>>>
>>> It is up to the community to decide whether these missing backports
>>> should be considered release blockers. Most of the corresponding PRs have
>>> already been merged to main (except #15512), and including them in the
>>> release should be relatively straightforward.
>>>
>>> From my perspective, I would prefer not to release with these gaps. That
>>> said, I understand the urgency and the need for a release, and I am happy
>>> to go with the community’s decision.
>>>
>>> Peter
>>>
>>> Aihua Xu  ezt írta (időpont: 2026. máj. 7., Cs,
>>> 18:26):
>>>
 Hi Everyone,

 I propose that we release the following RC as the official Apache
 Iceberg 1.11.0 release.

 The commit ID is 0f657edf12dc29f8487a679bfdd4210e9588d014
 * This corresponds to the tag: apache-iceberg-1.11.0-rc1
 * https://github.com/apache/iceberg/commits/apache-iceberg-1.11.0-rc1
 *
 https://github.com/apache/iceberg/tree/0f657edf12dc29f8487a679bfdd4210e9588d014

 The release tarball, signature, and checksums are here:
 *
 https://dist.apache.org/repos/dist/dev/iceberg/apache-iceberg-1.11.0-rc1

 You can find the KEYS file here:
 * https://downloads.apache.org/iceberg/KEYS

 Convenience binary artifacts are staged on Nexus. The Maven repository
 URL is:
 *
 https://repository.apache.org/content/repositories/orgapacheiceberg-1278/

 Please download, verify, and test.

 Instructions for verifying a release can be found here:
 * https://iceberg.apache.org/how-to-release/#how-to-verify-a-release

 Please vote in the next 72 hours.

 [ ] +1 Release this as Apache Iceberg 1.11.0
 [ ] +0
 [ ] -1 Do not release this because...

 Only PMC members have binding votes, but other community members are
 encouraged to cast
 non-binding votes. This vote will pass if there are 3 binding +1 votes
 and more binding
 +1 votes than -1 votes.

Re: [VOTE] Release Apache Iceberg 1.11.0 RC1

[Steven Wu]

Yuya, thanks for reporting the discovery.

Azure: I approved your PR and can merge it soon:
https://github.com/apache/iceberg/pull/16186
GCP: the new dependency is marked as compileOnly in PR 14333
, as it is an opt-in feature.
we need to either change the dep to implementation or update the code
similar to the Azure fix above.


On Thu, May 7, 2026 at 4:07 PM Yuya Ebihara 
wrote:

> Hi Aihua,
>
> Thanks for leading the release!
>
> Just a quick reminder about two dependency-related items from a downstream
> perspective:
> * Azure module users will require azure-security-keyvault-keys, even when
> table encryption is not used, as noted in
> https://github.com/apache/iceberg/pull/16186
> * GCS module users will require gcs-analytics-core
>
> I ran into CI failures with 1.11.0 in Trino because the project does not
> use the azure-bundle or gcp-bundle modules.
> The CI passed once we explicitly added these two dependencies.
>
> Thanks,
> Yuya Ebihara
>
> On Fri, May 8, 2026 at 4:58 AM Péter Váry 
> wrote:
>
>> First of all, thanks to everyone for the effort put into preparing this
>> release!
>>
>> I would like to highlight that RC1 is built from a branch where the
>> following features have not been backported to all engine versions:
>> - Spark: Support writing shredded variant in Iceberg-Spark (
>> https://github.com/apache/iceberg/pull/14297) - Available in Spark 4.1,
>> but not in Spark 4.0
>> - Spark: fix delete from branch for canDeleteWhere where it does not
>> resolve to the correct branch (
>> https://github.com/apache/iceberg/pull/15512) - Available in Spark 4.1,
>> but not in Spark 4.0, 3.5, or 3.4
>> - Flink: Add Nanosecond Precision Support for Flink-Iceberg Integration (
>> https://github.com/apache/iceberg/pull/15475) - Available in Flink 2.1,
>> but not in Flink 2.0 or 1.20
>>
>> It is up to the community to decide whether these missing backports
>> should be considered release blockers. Most of the corresponding PRs have
>> already been merged to main (except #15512), and including them in the
>> release should be relatively straightforward.
>>
>> From my perspective, I would prefer not to release with these gaps. That
>> said, I understand the urgency and the need for a release, and I am happy
>> to go with the community’s decision.
>>
>> Peter
>>
>> Aihua Xu  ezt írta (időpont: 2026. máj. 7., Cs,
>> 18:26):
>>
>>> Hi Everyone,
>>>
>>> I propose that we release the following RC as the official Apache
>>> Iceberg 1.11.0 release.
>>>
>>> The commit ID is 0f657edf12dc29f8487a679bfdd4210e9588d014
>>> * This corresponds to the tag: apache-iceberg-1.11.0-rc1
>>> * https://github.com/apache/iceberg/commits/apache-iceberg-1.11.0-rc1
>>> *
>>> https://github.com/apache/iceberg/tree/0f657edf12dc29f8487a679bfdd4210e9588d014
>>>
>>> The release tarball, signature, and checksums are here:
>>> *
>>> https://dist.apache.org/repos/dist/dev/iceberg/apache-iceberg-1.11.0-rc1
>>>
>>> You can find the KEYS file here:
>>> * https://downloads.apache.org/iceberg/KEYS
>>>
>>> Convenience binary artifacts are staged on Nexus. The Maven repository
>>> URL is:
>>> *
>>> https://repository.apache.org/content/repositories/orgapacheiceberg-1278/
>>>
>>> Please download, verify, and test.
>>>
>>> Instructions for verifying a release can be found here:
>>> * https://iceberg.apache.org/how-to-release/#how-to-verify-a-release
>>>
>>> Please vote in the next 72 hours.
>>>
>>> [ ] +1 Release this as Apache Iceberg 1.11.0
>>> [ ] +0
>>> [ ] -1 Do not release this because...
>>>
>>> Only PMC members have binding votes, but other community members are
>>> encouraged to cast
>>> non-binding votes. This vote will pass if there are 3 binding +1 votes
>>> and more binding
>>> +1 votes than -1 votes.
>>>
>>>

Re: [VOTE] Release Apache Iceberg 1.11.0 RC1

[Yuya Ebihara]

Hi Aihua,

Thanks for leading the release!

Just a quick reminder about two dependency-related items from a downstream
perspective:
* Azure module users will require azure-security-keyvault-keys, even when
table encryption is not used, as noted in
https://github.com/apache/iceberg/pull/16186
* GCS module users will require gcs-analytics-core

I ran into CI failures with 1.11.0 in Trino because the project does not
use the azure-bundle or gcp-bundle modules.
The CI passed once we explicitly added these two dependencies.

Thanks,
Yuya Ebihara

On Fri, May 8, 2026 at 4:58 AM Péter Váry 
wrote:

> First of all, thanks to everyone for the effort put into preparing this
> release!
>
> I would like to highlight that RC1 is built from a branch where the
> following features have not been backported to all engine versions:
> - Spark: Support writing shredded variant in Iceberg-Spark (
> https://github.com/apache/iceberg/pull/14297) - Available in Spark 4.1,
> but not in Spark 4.0
> - Spark: fix delete from branch for canDeleteWhere where it does not
> resolve to the correct branch (
> https://github.com/apache/iceberg/pull/15512) - Available in Spark 4.1,
> but not in Spark 4.0, 3.5, or 3.4
> - Flink: Add Nanosecond Precision Support for Flink-Iceberg Integration (
> https://github.com/apache/iceberg/pull/15475) - Available in Flink 2.1,
> but not in Flink 2.0 or 1.20
>
> It is up to the community to decide whether these missing backports should
> be considered release blockers. Most of the corresponding PRs have already
> been merged to main (except #15512), and including them in the release
> should be relatively straightforward.
>
> From my perspective, I would prefer not to release with these gaps. That
> said, I understand the urgency and the need for a release, and I am happy
> to go with the community’s decision.
>
> Peter
>
> Aihua Xu  ezt írta (időpont: 2026. máj. 7., Cs, 18:26):
>
>> Hi Everyone,
>>
>> I propose that we release the following RC as the official Apache Iceberg
>> 1.11.0 release.
>>
>> The commit ID is 0f657edf12dc29f8487a679bfdd4210e9588d014
>> * This corresponds to the tag: apache-iceberg-1.11.0-rc1
>> * https://github.com/apache/iceberg/commits/apache-iceberg-1.11.0-rc1
>> *
>> https://github.com/apache/iceberg/tree/0f657edf12dc29f8487a679bfdd4210e9588d014
>>
>> The release tarball, signature, and checksums are here:
>> *
>> https://dist.apache.org/repos/dist/dev/iceberg/apache-iceberg-1.11.0-rc1
>>
>> You can find the KEYS file here:
>> * https://downloads.apache.org/iceberg/KEYS
>>
>> Convenience binary artifacts are staged on Nexus. The Maven repository
>> URL is:
>> *
>> https://repository.apache.org/content/repositories/orgapacheiceberg-1278/
>>
>> Please download, verify, and test.
>>
>> Instructions for verifying a release can be found here:
>> * https://iceberg.apache.org/how-to-release/#how-to-verify-a-release
>>
>> Please vote in the next 72 hours.
>>
>> [ ] +1 Release this as Apache Iceberg 1.11.0
>> [ ] +0
>> [ ] -1 Do not release this because...
>>
>> Only PMC members have binding votes, but other community members are
>> encouraged to cast
>> non-binding votes. This vote will pass if there are 3 binding +1 votes
>> and more binding
>> +1 votes than -1 votes.
>>
>>

Re: [VOTE] Release Apache Iceberg 1.11.0 RC1

[Péter Váry]

First of all, thanks to everyone for the effort put into preparing this
release!

I would like to highlight that RC1 is built from a branch where the
following features have not been backported to all engine versions:
- Spark: Support writing shredded variant in Iceberg-Spark (
https://github.com/apache/iceberg/pull/14297) - Available in Spark 4.1, but
not in Spark 4.0
- Spark: fix delete from branch for canDeleteWhere where it does not
resolve to the correct branch (https://github.com/apache/iceberg/pull/15512)
- Available in Spark 4.1, but not in Spark 4.0, 3.5, or 3.4
- Flink: Add Nanosecond Precision Support for Flink-Iceberg Integration (
https://github.com/apache/iceberg/pull/15475) - Available in Flink 2.1, but
not in Flink 2.0 or 1.20

It is up to the community to decide whether these missing backports should
be considered release blockers. Most of the corresponding PRs have already
been merged to main (except #15512), and including them in the release
should be relatively straightforward.

>From my perspective, I would prefer not to release with these gaps. That
said, I understand the urgency and the need for a release, and I am happy
to go with the community’s decision.

Peter

Aihua Xu  ezt írta (időpont: 2026. máj. 7., Cs, 18:26):

> Hi Everyone,
>
> I propose that we release the following RC as the official Apache Iceberg
> 1.11.0 release.
>
> The commit ID is 0f657edf12dc29f8487a679bfdd4210e9588d014
> * This corresponds to the tag: apache-iceberg-1.11.0-rc1
> * https://github.com/apache/iceberg/commits/apache-iceberg-1.11.0-rc1
> *
> https://github.com/apache/iceberg/tree/0f657edf12dc29f8487a679bfdd4210e9588d014
>
> The release tarball, signature, and checksums are here:
> * https://dist.apache.org/repos/dist/dev/iceberg/apache-iceberg-1.11.0-rc1
>
> You can find the KEYS file here:
> * https://downloads.apache.org/iceberg/KEYS
>
> Convenience binary artifacts are staged on Nexus. The Maven repository URL
> is:
> *
> https://repository.apache.org/content/repositories/orgapacheiceberg-1278/
>
> Please download, verify, and test.
>
> Instructions for verifying a release can be found here:
> * https://iceberg.apache.org/how-to-release/#how-to-verify-a-release
>
> Please vote in the next 72 hours.
>
> [ ] +1 Release this as Apache Iceberg 1.11.0
> [ ] +0
> [ ] -1 Do not release this because...
>
> Only PMC members have binding votes, but other community members are
> encouraged to cast
> non-binding votes. This vote will pass if there are 3 binding +1 votes and
> more binding
> +1 votes than -1 votes.
>
>