Re: [VOTE] Release Apache Iceberg 1.9.1 RC1

[Russell Spitzer]

I'm +1 (Binding) as well so I'll close out this vote

On Tue, May 27, 2025 at 1:28 PM Aihua Xu  wrote:

> +1 (non-binding).
>
> Verified against Snowflake engine.
>
> On Tue, May 27, 2025 at 9:28 AM huaxin gao  wrote:
>
>> +1 (non-binding)
>> Verified signature, checksum, license and ran some tests.
>>
>> On Tue, May 27, 2025 at 9:06 AM Russell Spitzer <
>> russell.spit...@gmail.com> wrote:
>>
>>> For all those who haven't seen this before, GPG key signing is a very
>>> "early hacker" sort of thing. The idea is the only way to trust a signature
>>> is to
>>> have it signed by someone that you also trust. This builds a network of
>>> trust so you could essentially do something like say I trust that key X is
>>> Russell
>>> and therefore trust that Key Y signed by Key X is also trusted to be
>>> whoever they say they are because you trust Russell and his key. I don't
>>> think folks do
>>> this all that often any more but never fear, our current process is not
>>> "completely" anonymous.
>>>
>>> When you download the KEYS file from SVN you are downloading what is
>>> essentially a list of Public Keys and Identities that is updated only by
>>> folks
>>> with valid Apache SVN credentials so there is a bit of security there.
>>>
>>> All of that to say, yes that key is mine and if you trust that this
>>> email comes from me, you can trust that key is also me. If you don't trust
>>> this email ...
>>> send me a message and I can 1 on 1 verify with you on video (although
>>> with AI who knows) that I am Russell and that is my key. I'll be in SF in
>>> person next week for Snowflake Summit if anyone wants in person
>>> validation :)
>>>
>>>
>>> On Tue, May 27, 2025 at 10:38 AM Kevin Liu 
>>> wrote:
>>>
 +1 (non-binding)

 - Verified signature, checksum, license.
 * Build + test passed using Java 17 on M1
 * Ran a few examples on Spark
 * Ran pyiceberg integration tests

 Best,
 Kevin Liu

 On Tue, May 27, 2025 at 7:59 AM karuppayya 
 wrote:

> When verifying
> 
> signatures. I got a warning. Am I missing something with the gpg
> configuration?
>
> gpg: assuming signed data in 'apache-iceberg-1.9.1.tar.gz'
> gpg: Signature made Wed May 21 15:19:17 2025 PDT
> gpg:using RSA key xxx
> gpg: Good signature from "Russell Spitzer (CODE SIGNING KEY) 
> " [unknown]
> gpg: WARNING: This key is not certified with a trusted signature!
> gpg:  There is no indication that the signature belongs to the 
> owner.
> Primary key fingerprint: x
>
>
> Verified checksums, local build and ran basic tests on Spark 3.5.
>
> If the warning is ok to ignore,
> +1 (non-binding)
>
> - Karuppayya
>
>
>
>
> On Tue, May 27, 2025 at 7:29 AM Jean-Baptiste Onofré 
> wrote:
>
>> +1 (non binding)
>>
>> I checked:
>> * source distribution
>> ** checksum and signature are good
>> ** LICENSE and NOTICE look good
>> ** No binary file found in the source distribution
>> ** Header looks good in files
>> ** Build works from the source distribution
>> ** Tested with Spark and Polaris
>> * in the bundled jar files:
>> ** aws-bundle jar contains correct LICENSE/NOTICE
>> ** azure-bundle jar contains LICENSE/NOTICE, nit: Azure MIT license
>> content should be part of the LICENSE (inline). I will fix that.
>> ** gcp-bundle jar contains LICENSE/NOTICE, nit: Google BSD 3-Clause
>> license content should be part of the LICENSE (inline), and some
>> dependencies have dual licenses, only one should be "selected" in
>> Iceberg (exclusive). I will fix that.
>> ** kafka-runtime (main and hive) contains LICENSE/NOTICE, nit: same
>> issue as in azure-bundle and gcp-bundle about exclusive license and
>> MIT/BSD license content
>>
>> Regards
>> JB
>>
>> On Thu, May 22, 2025 at 1:19 AM Russell Spitzer
>>  wrote:
>> >
>> > Hi Y'all,
>> >
>> > I propose that we release the following RC as the official Apache
>> Iceberg 1.9.1 release.
>> >
>> > The commit ID is f40208ae6fb2f33e578c2637d3dea1db18739f31
>> > * This corresponds to the tag: apache-iceberg-1.9.1-rc1
>> > *
>> https://github.com/apache/iceberg/commits/apache-iceberg-1.9.1-rc1
>> > *
>> https://github.com/apache/iceberg/tree/f40208ae6fb2f33e578c2637d3dea1db18739f31
>> >
>> > The release tarball, signature, and checksums are here:
>> > *
>> https://dist.apache.org/repos/dist/dev/iceberg/apache-iceberg-1.9.1-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-1

Re: [VOTE] Release Apache Iceberg 1.9.1 RC1

[Aihua Xu]

+1 (non-binding).

Verified against Snowflake engine.

On Tue, May 27, 2025 at 9:28 AM huaxin gao  wrote:

> +1 (non-binding)
> Verified signature, checksum, license and ran some tests.
>
> On Tue, May 27, 2025 at 9:06 AM Russell Spitzer 
> wrote:
>
>> For all those who haven't seen this before, GPG key signing is a very
>> "early hacker" sort of thing. The idea is the only way to trust a signature
>> is to
>> have it signed by someone that you also trust. This builds a network of
>> trust so you could essentially do something like say I trust that key X is
>> Russell
>> and therefore trust that Key Y signed by Key X is also trusted to be
>> whoever they say they are because you trust Russell and his key. I don't
>> think folks do
>> this all that often any more but never fear, our current process is not
>> "completely" anonymous.
>>
>> When you download the KEYS file from SVN you are downloading what is
>> essentially a list of Public Keys and Identities that is updated only by
>> folks
>> with valid Apache SVN credentials so there is a bit of security there.
>>
>> All of that to say, yes that key is mine and if you trust that this email
>> comes from me, you can trust that key is also me. If you don't trust this
>> email ...
>> send me a message and I can 1 on 1 verify with you on video (although
>> with AI who knows) that I am Russell and that is my key. I'll be in SF in
>> person next week for Snowflake Summit if anyone wants in person
>> validation :)
>>
>>
>> On Tue, May 27, 2025 at 10:38 AM Kevin Liu  wrote:
>>
>>> +1 (non-binding)
>>>
>>> - Verified signature, checksum, license.
>>> * Build + test passed using Java 17 on M1
>>> * Ran a few examples on Spark
>>> * Ran pyiceberg integration tests
>>>
>>> Best,
>>> Kevin Liu
>>>
>>> On Tue, May 27, 2025 at 7:59 AM karuppayya 
>>> wrote:
>>>
 When verifying
 
 signatures. I got a warning. Am I missing something with the gpg
 configuration?

 gpg: assuming signed data in 'apache-iceberg-1.9.1.tar.gz'
 gpg: Signature made Wed May 21 15:19:17 2025 PDT
 gpg:using RSA key xxx
 gpg: Good signature from "Russell Spitzer (CODE SIGNING KEY) 
 " [unknown]
 gpg: WARNING: This key is not certified with a trusted signature!
 gpg:  There is no indication that the signature belongs to the 
 owner.
 Primary key fingerprint: x


 Verified checksums, local build and ran basic tests on Spark 3.5.

 If the warning is ok to ignore,
 +1 (non-binding)

 - Karuppayya




 On Tue, May 27, 2025 at 7:29 AM Jean-Baptiste Onofré 
 wrote:

> +1 (non binding)
>
> I checked:
> * source distribution
> ** checksum and signature are good
> ** LICENSE and NOTICE look good
> ** No binary file found in the source distribution
> ** Header looks good in files
> ** Build works from the source distribution
> ** Tested with Spark and Polaris
> * in the bundled jar files:
> ** aws-bundle jar contains correct LICENSE/NOTICE
> ** azure-bundle jar contains LICENSE/NOTICE, nit: Azure MIT license
> content should be part of the LICENSE (inline). I will fix that.
> ** gcp-bundle jar contains LICENSE/NOTICE, nit: Google BSD 3-Clause
> license content should be part of the LICENSE (inline), and some
> dependencies have dual licenses, only one should be "selected" in
> Iceberg (exclusive). I will fix that.
> ** kafka-runtime (main and hive) contains LICENSE/NOTICE, nit: same
> issue as in azure-bundle and gcp-bundle about exclusive license and
> MIT/BSD license content
>
> Regards
> JB
>
> On Thu, May 22, 2025 at 1:19 AM Russell Spitzer
>  wrote:
> >
> > Hi Y'all,
> >
> > I propose that we release the following RC as the official Apache
> Iceberg 1.9.1 release.
> >
> > The commit ID is f40208ae6fb2f33e578c2637d3dea1db18739f31
> > * This corresponds to the tag: apache-iceberg-1.9.1-rc1
> > * https://github.com/apache/iceberg/commits/apache-iceberg-1.9.1-rc1
> > *
> https://github.com/apache/iceberg/tree/f40208ae6fb2f33e578c2637d3dea1db18739f31
> >
> > The release tarball, signature, and checksums are here:
> > *
> https://dist.apache.org/repos/dist/dev/iceberg/apache-iceberg-1.9.1-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-1202/
> >
> > Please download, verify, and test.
> >
> > Please vote in the next 72 hours.
> >
> > [ ] +1 Release this as Apache Iceberg 1.9.1
> > [ ] +0
> > [ ] -1 Do not release this because...
> >
> > Only PMC members have binding votes

Re: [VOTE] Release Apache Iceberg 1.9.1 RC1

[huaxin gao]

+1 (non-binding)
Verified signature, checksum, license and ran some tests.

On Tue, May 27, 2025 at 9:06 AM Russell Spitzer 
wrote:

> For all those who haven't seen this before, GPG key signing is a very
> "early hacker" sort of thing. The idea is the only way to trust a signature
> is to
> have it signed by someone that you also trust. This builds a network of
> trust so you could essentially do something like say I trust that key X is
> Russell
> and therefore trust that Key Y signed by Key X is also trusted to be
> whoever they say they are because you trust Russell and his key. I don't
> think folks do
> this all that often any more but never fear, our current process is not
> "completely" anonymous.
>
> When you download the KEYS file from SVN you are downloading what is
> essentially a list of Public Keys and Identities that is updated only by
> folks
> with valid Apache SVN credentials so there is a bit of security there.
>
> All of that to say, yes that key is mine and if you trust that this email
> comes from me, you can trust that key is also me. If you don't trust this
> email ...
> send me a message and I can 1 on 1 verify with you on video (although with
> AI who knows) that I am Russell and that is my key. I'll be in SF in
> person next week for Snowflake Summit if anyone wants in person validation
> :)
>
>
> On Tue, May 27, 2025 at 10:38 AM Kevin Liu  wrote:
>
>> +1 (non-binding)
>>
>> - Verified signature, checksum, license.
>> * Build + test passed using Java 17 on M1
>> * Ran a few examples on Spark
>> * Ran pyiceberg integration tests
>>
>> Best,
>> Kevin Liu
>>
>> On Tue, May 27, 2025 at 7:59 AM karuppayya 
>> wrote:
>>
>>> When verifying
>>> 
>>> signatures. I got a warning. Am I missing something with the gpg
>>> configuration?
>>>
>>> gpg: assuming signed data in 'apache-iceberg-1.9.1.tar.gz'
>>> gpg: Signature made Wed May 21 15:19:17 2025 PDT
>>> gpg:using RSA key xxx
>>> gpg: Good signature from "Russell Spitzer (CODE SIGNING KEY) 
>>> " [unknown]
>>> gpg: WARNING: This key is not certified with a trusted signature!
>>> gpg:  There is no indication that the signature belongs to the 
>>> owner.
>>> Primary key fingerprint: x
>>>
>>>
>>> Verified checksums, local build and ran basic tests on Spark 3.5.
>>>
>>> If the warning is ok to ignore,
>>> +1 (non-binding)
>>>
>>> - Karuppayya
>>>
>>>
>>>
>>>
>>> On Tue, May 27, 2025 at 7:29 AM Jean-Baptiste Onofré 
>>> wrote:
>>>
 +1 (non binding)

 I checked:
 * source distribution
 ** checksum and signature are good
 ** LICENSE and NOTICE look good
 ** No binary file found in the source distribution
 ** Header looks good in files
 ** Build works from the source distribution
 ** Tested with Spark and Polaris
 * in the bundled jar files:
 ** aws-bundle jar contains correct LICENSE/NOTICE
 ** azure-bundle jar contains LICENSE/NOTICE, nit: Azure MIT license
 content should be part of the LICENSE (inline). I will fix that.
 ** gcp-bundle jar contains LICENSE/NOTICE, nit: Google BSD 3-Clause
 license content should be part of the LICENSE (inline), and some
 dependencies have dual licenses, only one should be "selected" in
 Iceberg (exclusive). I will fix that.
 ** kafka-runtime (main and hive) contains LICENSE/NOTICE, nit: same
 issue as in azure-bundle and gcp-bundle about exclusive license and
 MIT/BSD license content

 Regards
 JB

 On Thu, May 22, 2025 at 1:19 AM Russell Spitzer
  wrote:
 >
 > Hi Y'all,
 >
 > I propose that we release the following RC as the official Apache
 Iceberg 1.9.1 release.
 >
 > The commit ID is f40208ae6fb2f33e578c2637d3dea1db18739f31
 > * This corresponds to the tag: apache-iceberg-1.9.1-rc1
 > * https://github.com/apache/iceberg/commits/apache-iceberg-1.9.1-rc1
 > *
 https://github.com/apache/iceberg/tree/f40208ae6fb2f33e578c2637d3dea1db18739f31
 >
 > The release tarball, signature, and checksums are here:
 > *
 https://dist.apache.org/repos/dist/dev/iceberg/apache-iceberg-1.9.1-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-1202/
 >
 > Please download, verify, and test.
 >
 > Please vote in the next 72 hours.
 >
 > [ ] +1 Release this as Apache Iceberg 1.9.1
 > [ ] +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.
 >
 > ---
 >
 > For those watching the big

Re: [VOTE] Release Apache Iceberg 1.9.1 RC1

[Russell Spitzer]

For all those who haven't seen this before, GPG key signing is a very
"early hacker" sort of thing. The idea is the only way to trust a signature
is to
have it signed by someone that you also trust. This builds a network of
trust so you could essentially do something like say I trust that key X is
Russell
and therefore trust that Key Y signed by Key X is also trusted to be
whoever they say they are because you trust Russell and his key. I don't
think folks do
this all that often any more but never fear, our current process is not
"completely" anonymous.

When you download the KEYS file from SVN you are downloading what is
essentially a list of Public Keys and Identities that is updated only by
folks
with valid Apache SVN credentials so there is a bit of security there.

All of that to say, yes that key is mine and if you trust that this email
comes from me, you can trust that key is also me. If you don't trust this
email ...
send me a message and I can 1 on 1 verify with you on video (although with
AI who knows) that I am Russell and that is my key. I'll be in SF in
person next week for Snowflake Summit if anyone wants in person validation
:)


On Tue, May 27, 2025 at 10:38 AM Kevin Liu  wrote:

> +1 (non-binding)
>
> - Verified signature, checksum, license.
> * Build + test passed using Java 17 on M1
> * Ran a few examples on Spark
> * Ran pyiceberg integration tests
>
> Best,
> Kevin Liu
>
> On Tue, May 27, 2025 at 7:59 AM karuppayya 
> wrote:
>
>> When verifying
>> 
>> signatures. I got a warning. Am I missing something with the gpg
>> configuration?
>>
>> gpg: assuming signed data in 'apache-iceberg-1.9.1.tar.gz'
>> gpg: Signature made Wed May 21 15:19:17 2025 PDT
>> gpg:using RSA key xxx
>> gpg: Good signature from "Russell Spitzer (CODE SIGNING KEY) 
>> " [unknown]
>> gpg: WARNING: This key is not certified with a trusted signature!
>> gpg:  There is no indication that the signature belongs to the owner.
>> Primary key fingerprint: x
>>
>>
>> Verified checksums, local build and ran basic tests on Spark 3.5.
>>
>> If the warning is ok to ignore,
>> +1 (non-binding)
>>
>> - Karuppayya
>>
>>
>>
>>
>> On Tue, May 27, 2025 at 7:29 AM Jean-Baptiste Onofré 
>> wrote:
>>
>>> +1 (non binding)
>>>
>>> I checked:
>>> * source distribution
>>> ** checksum and signature are good
>>> ** LICENSE and NOTICE look good
>>> ** No binary file found in the source distribution
>>> ** Header looks good in files
>>> ** Build works from the source distribution
>>> ** Tested with Spark and Polaris
>>> * in the bundled jar files:
>>> ** aws-bundle jar contains correct LICENSE/NOTICE
>>> ** azure-bundle jar contains LICENSE/NOTICE, nit: Azure MIT license
>>> content should be part of the LICENSE (inline). I will fix that.
>>> ** gcp-bundle jar contains LICENSE/NOTICE, nit: Google BSD 3-Clause
>>> license content should be part of the LICENSE (inline), and some
>>> dependencies have dual licenses, only one should be "selected" in
>>> Iceberg (exclusive). I will fix that.
>>> ** kafka-runtime (main and hive) contains LICENSE/NOTICE, nit: same
>>> issue as in azure-bundle and gcp-bundle about exclusive license and
>>> MIT/BSD license content
>>>
>>> Regards
>>> JB
>>>
>>> On Thu, May 22, 2025 at 1:19 AM Russell Spitzer
>>>  wrote:
>>> >
>>> > Hi Y'all,
>>> >
>>> > I propose that we release the following RC as the official Apache
>>> Iceberg 1.9.1 release.
>>> >
>>> > The commit ID is f40208ae6fb2f33e578c2637d3dea1db18739f31
>>> > * This corresponds to the tag: apache-iceberg-1.9.1-rc1
>>> > * https://github.com/apache/iceberg/commits/apache-iceberg-1.9.1-rc1
>>> > *
>>> https://github.com/apache/iceberg/tree/f40208ae6fb2f33e578c2637d3dea1db18739f31
>>> >
>>> > The release tarball, signature, and checksums are here:
>>> > *
>>> https://dist.apache.org/repos/dist/dev/iceberg/apache-iceberg-1.9.1-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-1202/
>>> >
>>> > Please download, verify, and test.
>>> >
>>> > Please vote in the next 72 hours.
>>> >
>>> > [ ] +1 Release this as Apache Iceberg 1.9.1
>>> > [ ] +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.
>>> >
>>> > ---
>>> >
>>> > For those watching the big change between this and RC0 was the
>>> reversion of code which
>>> > caused the rest client to emit multiple Snapshot Removals Requests in
>>> the same MetadataUpdate.
>>> > This restores the behavior to that of 1.8.X, 1 removal per update.
>>> > We plan to move to the new behavior in a later re

Re: [VOTE] Release Apache Iceberg 1.9.1 RC1

[Kevin Liu]

+1 (non-binding)

- Verified signature, checksum, license.
* Build + test passed using Java 17 on M1
* Ran a few examples on Spark
* Ran pyiceberg integration tests

Best,
Kevin Liu

On Tue, May 27, 2025 at 7:59 AM karuppayya  wrote:

> When verifying
> 
> signatures. I got a warning. Am I missing something with the gpg
> configuration?
>
> gpg: assuming signed data in 'apache-iceberg-1.9.1.tar.gz'
> gpg: Signature made Wed May 21 15:19:17 2025 PDT
> gpg:using RSA key xxx
> gpg: Good signature from "Russell Spitzer (CODE SIGNING KEY) 
> " [unknown]
> gpg: WARNING: This key is not certified with a trusted signature!
> gpg:  There is no indication that the signature belongs to the owner.
> Primary key fingerprint: x
>
>
> Verified checksums, local build and ran basic tests on Spark 3.5.
>
> If the warning is ok to ignore,
> +1 (non-binding)
>
> - Karuppayya
>
>
>
>
> On Tue, May 27, 2025 at 7:29 AM Jean-Baptiste Onofré 
> wrote:
>
>> +1 (non binding)
>>
>> I checked:
>> * source distribution
>> ** checksum and signature are good
>> ** LICENSE and NOTICE look good
>> ** No binary file found in the source distribution
>> ** Header looks good in files
>> ** Build works from the source distribution
>> ** Tested with Spark and Polaris
>> * in the bundled jar files:
>> ** aws-bundle jar contains correct LICENSE/NOTICE
>> ** azure-bundle jar contains LICENSE/NOTICE, nit: Azure MIT license
>> content should be part of the LICENSE (inline). I will fix that.
>> ** gcp-bundle jar contains LICENSE/NOTICE, nit: Google BSD 3-Clause
>> license content should be part of the LICENSE (inline), and some
>> dependencies have dual licenses, only one should be "selected" in
>> Iceberg (exclusive). I will fix that.
>> ** kafka-runtime (main and hive) contains LICENSE/NOTICE, nit: same
>> issue as in azure-bundle and gcp-bundle about exclusive license and
>> MIT/BSD license content
>>
>> Regards
>> JB
>>
>> On Thu, May 22, 2025 at 1:19 AM Russell Spitzer
>>  wrote:
>> >
>> > Hi Y'all,
>> >
>> > I propose that we release the following RC as the official Apache
>> Iceberg 1.9.1 release.
>> >
>> > The commit ID is f40208ae6fb2f33e578c2637d3dea1db18739f31
>> > * This corresponds to the tag: apache-iceberg-1.9.1-rc1
>> > * https://github.com/apache/iceberg/commits/apache-iceberg-1.9.1-rc1
>> > *
>> https://github.com/apache/iceberg/tree/f40208ae6fb2f33e578c2637d3dea1db18739f31
>> >
>> > The release tarball, signature, and checksums are here:
>> > *
>> https://dist.apache.org/repos/dist/dev/iceberg/apache-iceberg-1.9.1-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-1202/
>> >
>> > Please download, verify, and test.
>> >
>> > Please vote in the next 72 hours.
>> >
>> > [ ] +1 Release this as Apache Iceberg 1.9.1
>> > [ ] +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.
>> >
>> > ---
>> >
>> > For those watching the big change between this and RC0 was the
>> reversion of code which
>> > caused the rest client to emit multiple Snapshot Removals Requests in
>> the same MetadataUpdate.
>> > This restores the behavior to that of 1.8.X, 1 removal per update.
>> > We plan to move to the new behavior in a later release
>>
>

Re: [VOTE] Release Apache Iceberg 1.9.1 RC1

[karuppayya]

When verifying

signatures. I got a warning. Am I missing something with the gpg
configuration?

gpg: assuming signed data in 'apache-iceberg-1.9.1.tar.gz'
gpg: Signature made Wed May 21 15:19:17 2025 PDT
gpg:using RSA key xxx
gpg: Good signature from "Russell Spitzer (CODE SIGNING KEY)
" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:  There is no indication that the signature belongs to the owner.
Primary key fingerprint: x


Verified checksums, local build and ran basic tests on Spark 3.5.

If the warning is ok to ignore,
+1 (non-binding)

- Karuppayya




On Tue, May 27, 2025 at 7:29 AM Jean-Baptiste Onofré 
wrote:

> +1 (non binding)
>
> I checked:
> * source distribution
> ** checksum and signature are good
> ** LICENSE and NOTICE look good
> ** No binary file found in the source distribution
> ** Header looks good in files
> ** Build works from the source distribution
> ** Tested with Spark and Polaris
> * in the bundled jar files:
> ** aws-bundle jar contains correct LICENSE/NOTICE
> ** azure-bundle jar contains LICENSE/NOTICE, nit: Azure MIT license
> content should be part of the LICENSE (inline). I will fix that.
> ** gcp-bundle jar contains LICENSE/NOTICE, nit: Google BSD 3-Clause
> license content should be part of the LICENSE (inline), and some
> dependencies have dual licenses, only one should be "selected" in
> Iceberg (exclusive). I will fix that.
> ** kafka-runtime (main and hive) contains LICENSE/NOTICE, nit: same
> issue as in azure-bundle and gcp-bundle about exclusive license and
> MIT/BSD license content
>
> Regards
> JB
>
> On Thu, May 22, 2025 at 1:19 AM Russell Spitzer
>  wrote:
> >
> > Hi Y'all,
> >
> > I propose that we release the following RC as the official Apache
> Iceberg 1.9.1 release.
> >
> > The commit ID is f40208ae6fb2f33e578c2637d3dea1db18739f31
> > * This corresponds to the tag: apache-iceberg-1.9.1-rc1
> > * https://github.com/apache/iceberg/commits/apache-iceberg-1.9.1-rc1
> > *
> https://github.com/apache/iceberg/tree/f40208ae6fb2f33e578c2637d3dea1db18739f31
> >
> > The release tarball, signature, and checksums are here:
> > *
> https://dist.apache.org/repos/dist/dev/iceberg/apache-iceberg-1.9.1-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-1202/
> >
> > Please download, verify, and test.
> >
> > Please vote in the next 72 hours.
> >
> > [ ] +1 Release this as Apache Iceberg 1.9.1
> > [ ] +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.
> >
> > ---
> >
> > For those watching the big change between this and RC0 was the reversion
> of code which
> > caused the rest client to emit multiple Snapshot Removals Requests in
> the same MetadataUpdate.
> > This restores the behavior to that of 1.8.X, 1 removal per update.
> > We plan to move to the new behavior in a later release
>

Re: [VOTE] Release Apache Iceberg 1.9.1 RC1

[Jean-Baptiste Onofré]

+1 (non binding)

I checked:
* source distribution
** checksum and signature are good
** LICENSE and NOTICE look good
** No binary file found in the source distribution
** Header looks good in files
** Build works from the source distribution
** Tested with Spark and Polaris
* in the bundled jar files:
** aws-bundle jar contains correct LICENSE/NOTICE
** azure-bundle jar contains LICENSE/NOTICE, nit: Azure MIT license
content should be part of the LICENSE (inline). I will fix that.
** gcp-bundle jar contains LICENSE/NOTICE, nit: Google BSD 3-Clause
license content should be part of the LICENSE (inline), and some
dependencies have dual licenses, only one should be "selected" in
Iceberg (exclusive). I will fix that.
** kafka-runtime (main and hive) contains LICENSE/NOTICE, nit: same
issue as in azure-bundle and gcp-bundle about exclusive license and
MIT/BSD license content

Regards
JB

On Thu, May 22, 2025 at 1:19 AM Russell Spitzer
 wrote:
>
> Hi Y'all,
>
> I propose that we release the following RC as the official Apache Iceberg 
> 1.9.1 release.
>
> The commit ID is f40208ae6fb2f33e578c2637d3dea1db18739f31
> * This corresponds to the tag: apache-iceberg-1.9.1-rc1
> * https://github.com/apache/iceberg/commits/apache-iceberg-1.9.1-rc1
> * 
> https://github.com/apache/iceberg/tree/f40208ae6fb2f33e578c2637d3dea1db18739f31
>
> The release tarball, signature, and checksums are here:
> * https://dist.apache.org/repos/dist/dev/iceberg/apache-iceberg-1.9.1-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-1202/
>
> Please download, verify, and test.
>
> Please vote in the next 72 hours.
>
> [ ] +1 Release this as Apache Iceberg 1.9.1
> [ ] +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.
>
> ---
>
> For those watching the big change between this and RC0 was the reversion of 
> code which
> caused the rest client to emit multiple Snapshot Removals Requests in the 
> same MetadataUpdate.
> This restores the behavior to that of 1.8.X, 1 removal per update.
> We plan to move to the new behavior in a later release

Re: [VOTE] Release Apache Iceberg 1.9.1 RC1

[Fokko Driesprong]

+1 (binding)

Ran signatures/checksums/tests/license

Kind regards,
Fokko

Op di 27 mei 2025 om 14:48 schreef Péter Váry :

> +1 (binding)
> tested signatures, built, run some tests
>
> Ajantha Bhat  ezt írta (időpont: 2025. máj. 27.,
> K, 14:40):
>
>> +1 (non-binding)
>>
>> * validated checksum and signature
>> * checked license docs & ran RAT checks
>> * ran build and tests
>>
>> - Ajantha
>>
>>
>> On Tue, May 27, 2025 at 7:19 AM Yuya Ebihara <
>> yuya.ebih...@starburstdata.com> wrote:
>>
>>> +1 (non-binding)
>>>
>>> Confirmed that Trino and Starburst CI are green.
>>> It runs tests against several catalogs, including HMS, Glue, JDBC
>>> (PostgreSQL), REST (Polaris, Unity, S3 Tables, Tabular), Nessie, and
>>> Snowflake.
>>>
>>> Yuya
>>>
>>> On Sat, May 24, 2025 at 7:37 AM Steven Wu  wrote:
>>>
 +1 (binding)

 Checked signature, checksum, and licenses.
 "./gradlew build" passed with the source bundle.
 Ran Flink 1.20 with SQL

 On Fri, May 23, 2025 at 10:42 AM Russell Spitzer <
 russell.spit...@gmail.com> wrote:

> Discussion was back here -
> https://lists.apache.org/thread/497qxkq3nfplwo27fh959zhsc2o7hkmy
>
> On Thu, May 22, 2025 at 12:09 AM Ajantha Bhat 
> wrote:
>
>> Thanks Ebihara for pointing me to the change.
>>
>> We should probably capture end user related changes in the release
>> notes (separate section).
>> I will close that issue.
>>
>> I am good with this RC. I will test and vote.
>>
>> On Thu, May 22, 2025 at 10:26 AM Yuya Ebihara <
>> yuya.ebih...@starburstdata.com> wrote:
>>
>>> Hi Ajantha,
>>>
>>> https://github.com/apache/iceberg/pull/12318 made JSON un-pretty
>>> for reduing the file size.
>>>
>>> BR,
>>> Yuya
>>>
>>> On Thu, May 22, 2025 at 1:52 PM Ajantha Bhat 
>>> wrote:
>>>
 Hi Russell,

 Just observed this change (table metadata JSON file is not
 formatted anymore)
 https://github.com/apache/iceberg/issues/13122

 If it is induced by 1.9.0, we should probably fix it and include it
 in RC?
 No functional impact.

 - Ajantha

 On Thu, May 22, 2025 at 4:49 AM Russell Spitzer <
 russell.spit...@gmail.com> wrote:

> Hi Y'all,
>
> I propose that we release the following RC as the official Apache
> Iceberg 1.9.1 release.
>
> The commit ID is f40208ae6fb2f33e578c2637d3dea1db18739f31
> * This corresponds to the tag: apache-iceberg-1.9.1-rc1
> *
> https://github.com/apache/iceberg/commits/apache-iceberg-1.9.1-rc1
> *
> https://github.com/apache/iceberg/tree/f40208ae6fb2f33e578c2637d3dea1db18739f31
>
> The release tarball, signature, and checksums are here:
> *
> https://dist.apache.org/repos/dist/dev/iceberg/apache-iceberg-1.9.1-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-1202/
>
> Please download, verify, and test.
>
> Please vote in the next 72 hours.
>
> [ ] +1 Release this as Apache Iceberg 1.9.1
> [ ] +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.
>
> ---
>
> For those watching the big change between this and RC0 was the
> reversion of code which
> caused the rest client to emit multiple Snapshot Removals Requests
> in the same MetadataUpdate.
> This restores the behavior to that of 1.8.X, 1 removal per update.
> We plan to move to the new behavior in a later release
>

Re: [VOTE] Release Apache Iceberg 1.9.1 RC1

[Péter Váry]

+1 (binding)
tested signatures, built, run some tests

Ajantha Bhat  ezt írta (időpont: 2025. máj. 27., K,
14:40):

> +1 (non-binding)
>
> * validated checksum and signature
> * checked license docs & ran RAT checks
> * ran build and tests
>
> - Ajantha
>
>
> On Tue, May 27, 2025 at 7:19 AM Yuya Ebihara <
> yuya.ebih...@starburstdata.com> wrote:
>
>> +1 (non-binding)
>>
>> Confirmed that Trino and Starburst CI are green.
>> It runs tests against several catalogs, including HMS, Glue, JDBC
>> (PostgreSQL), REST (Polaris, Unity, S3 Tables, Tabular), Nessie, and
>> Snowflake.
>>
>> Yuya
>>
>> On Sat, May 24, 2025 at 7:37 AM Steven Wu  wrote:
>>
>>> +1 (binding)
>>>
>>> Checked signature, checksum, and licenses.
>>> "./gradlew build" passed with the source bundle.
>>> Ran Flink 1.20 with SQL
>>>
>>> On Fri, May 23, 2025 at 10:42 AM Russell Spitzer <
>>> russell.spit...@gmail.com> wrote:
>>>
 Discussion was back here -
 https://lists.apache.org/thread/497qxkq3nfplwo27fh959zhsc2o7hkmy

 On Thu, May 22, 2025 at 12:09 AM Ajantha Bhat 
 wrote:

> Thanks Ebihara for pointing me to the change.
>
> We should probably capture end user related changes in the release
> notes (separate section).
> I will close that issue.
>
> I am good with this RC. I will test and vote.
>
> On Thu, May 22, 2025 at 10:26 AM Yuya Ebihara <
> yuya.ebih...@starburstdata.com> wrote:
>
>> Hi Ajantha,
>>
>> https://github.com/apache/iceberg/pull/12318 made JSON un-pretty for
>> reduing the file size.
>>
>> BR,
>> Yuya
>>
>> On Thu, May 22, 2025 at 1:52 PM Ajantha Bhat 
>> wrote:
>>
>>> Hi Russell,
>>>
>>> Just observed this change (table metadata JSON file is not formatted
>>> anymore)
>>> https://github.com/apache/iceberg/issues/13122
>>>
>>> If it is induced by 1.9.0, we should probably fix it and include it
>>> in RC?
>>> No functional impact.
>>>
>>> - Ajantha
>>>
>>> On Thu, May 22, 2025 at 4:49 AM Russell Spitzer <
>>> russell.spit...@gmail.com> wrote:
>>>
 Hi Y'all,

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

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

 The release tarball, signature, and checksums are here:
 *
 https://dist.apache.org/repos/dist/dev/iceberg/apache-iceberg-1.9.1-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-1202/

 Please download, verify, and test.

 Please vote in the next 72 hours.

 [ ] +1 Release this as Apache Iceberg 1.9.1
 [ ] +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.

 ---

 For those watching the big change between this and RC0 was the
 reversion of code which
 caused the rest client to emit multiple Snapshot Removals Requests
 in the same MetadataUpdate.
 This restores the behavior to that of 1.8.X, 1 removal per update.
 We plan to move to the new behavior in a later release

>>>

Re: [VOTE] Release Apache Iceberg 1.9.1 RC1

[Ajantha Bhat]

+1 (non-binding)

* validated checksum and signature
* checked license docs & ran RAT checks
* ran build and tests

- Ajantha


On Tue, May 27, 2025 at 7:19 AM Yuya Ebihara 
wrote:

> +1 (non-binding)
>
> Confirmed that Trino and Starburst CI are green.
> It runs tests against several catalogs, including HMS, Glue, JDBC
> (PostgreSQL), REST (Polaris, Unity, S3 Tables, Tabular), Nessie, and
> Snowflake.
>
> Yuya
>
> On Sat, May 24, 2025 at 7:37 AM Steven Wu  wrote:
>
>> +1 (binding)
>>
>> Checked signature, checksum, and licenses.
>> "./gradlew build" passed with the source bundle.
>> Ran Flink 1.20 with SQL
>>
>> On Fri, May 23, 2025 at 10:42 AM Russell Spitzer <
>> russell.spit...@gmail.com> wrote:
>>
>>> Discussion was back here -
>>> https://lists.apache.org/thread/497qxkq3nfplwo27fh959zhsc2o7hkmy
>>>
>>> On Thu, May 22, 2025 at 12:09 AM Ajantha Bhat 
>>> wrote:
>>>
 Thanks Ebihara for pointing me to the change.

 We should probably capture end user related changes in the release
 notes (separate section).
 I will close that issue.

 I am good with this RC. I will test and vote.

 On Thu, May 22, 2025 at 10:26 AM Yuya Ebihara <
 yuya.ebih...@starburstdata.com> wrote:

> Hi Ajantha,
>
> https://github.com/apache/iceberg/pull/12318 made JSON un-pretty for
> reduing the file size.
>
> BR,
> Yuya
>
> On Thu, May 22, 2025 at 1:52 PM Ajantha Bhat 
> wrote:
>
>> Hi Russell,
>>
>> Just observed this change (table metadata JSON file is not formatted
>> anymore)
>> https://github.com/apache/iceberg/issues/13122
>>
>> If it is induced by 1.9.0, we should probably fix it and include it
>> in RC?
>> No functional impact.
>>
>> - Ajantha
>>
>> On Thu, May 22, 2025 at 4:49 AM Russell Spitzer <
>> russell.spit...@gmail.com> wrote:
>>
>>> Hi Y'all,
>>>
>>> I propose that we release the following RC as the official Apache
>>> Iceberg 1.9.1 release.
>>>
>>> The commit ID is f40208ae6fb2f33e578c2637d3dea1db18739f31
>>> * This corresponds to the tag: apache-iceberg-1.9.1-rc1
>>> * https://github.com/apache/iceberg/commits/apache-iceberg-1.9.1-rc1
>>> *
>>> https://github.com/apache/iceberg/tree/f40208ae6fb2f33e578c2637d3dea1db18739f31
>>>
>>> The release tarball, signature, and checksums are here:
>>> *
>>> https://dist.apache.org/repos/dist/dev/iceberg/apache-iceberg-1.9.1-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-1202/
>>>
>>> Please download, verify, and test.
>>>
>>> Please vote in the next 72 hours.
>>>
>>> [ ] +1 Release this as Apache Iceberg 1.9.1
>>> [ ] +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.
>>>
>>> ---
>>>
>>> For those watching the big change between this and RC0 was the
>>> reversion of code which
>>> caused the rest client to emit multiple Snapshot Removals Requests
>>> in the same MetadataUpdate.
>>> This restores the behavior to that of 1.8.X, 1 removal per update.
>>> We plan to move to the new behavior in a later release
>>>
>>

Re: [VOTE] Release Apache Iceberg 1.9.1 RC1

[Yuya Ebihara]

+1 (non-binding)

Confirmed that Trino and Starburst CI are green.
It runs tests against several catalogs, including HMS, Glue, JDBC
(PostgreSQL), REST (Polaris, Unity, S3 Tables, Tabular), Nessie, and
Snowflake.

Yuya

On Sat, May 24, 2025 at 7:37 AM Steven Wu  wrote:

> +1 (binding)
>
> Checked signature, checksum, and licenses.
> "./gradlew build" passed with the source bundle.
> Ran Flink 1.20 with SQL
>
> On Fri, May 23, 2025 at 10:42 AM Russell Spitzer <
> russell.spit...@gmail.com> wrote:
>
>> Discussion was back here -
>> https://lists.apache.org/thread/497qxkq3nfplwo27fh959zhsc2o7hkmy
>>
>> On Thu, May 22, 2025 at 12:09 AM Ajantha Bhat 
>> wrote:
>>
>>> Thanks Ebihara for pointing me to the change.
>>>
>>> We should probably capture end user related changes in the release notes
>>> (separate section).
>>> I will close that issue.
>>>
>>> I am good with this RC. I will test and vote.
>>>
>>> On Thu, May 22, 2025 at 10:26 AM Yuya Ebihara <
>>> yuya.ebih...@starburstdata.com> wrote:
>>>
 Hi Ajantha,

 https://github.com/apache/iceberg/pull/12318 made JSON un-pretty for
 reduing the file size.

 BR,
 Yuya

 On Thu, May 22, 2025 at 1:52 PM Ajantha Bhat 
 wrote:

> Hi Russell,
>
> Just observed this change (table metadata JSON file is not formatted
> anymore)
> https://github.com/apache/iceberg/issues/13122
>
> If it is induced by 1.9.0, we should probably fix it and include it in
> RC?
> No functional impact.
>
> - Ajantha
>
> On Thu, May 22, 2025 at 4:49 AM Russell Spitzer <
> russell.spit...@gmail.com> wrote:
>
>> Hi Y'all,
>>
>> I propose that we release the following RC as the official Apache
>> Iceberg 1.9.1 release.
>>
>> The commit ID is f40208ae6fb2f33e578c2637d3dea1db18739f31
>> * This corresponds to the tag: apache-iceberg-1.9.1-rc1
>> * https://github.com/apache/iceberg/commits/apache-iceberg-1.9.1-rc1
>> *
>> https://github.com/apache/iceberg/tree/f40208ae6fb2f33e578c2637d3dea1db18739f31
>>
>> The release tarball, signature, and checksums are here:
>> *
>> https://dist.apache.org/repos/dist/dev/iceberg/apache-iceberg-1.9.1-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-1202/
>>
>> Please download, verify, and test.
>>
>> Please vote in the next 72 hours.
>>
>> [ ] +1 Release this as Apache Iceberg 1.9.1
>> [ ] +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.
>>
>> ---
>>
>> For those watching the big change between this and RC0 was the
>> reversion of code which
>> caused the rest client to emit multiple Snapshot Removals Requests in
>> the same MetadataUpdate.
>> This restores the behavior to that of 1.8.X, 1 removal per update.
>> We plan to move to the new behavior in a later release
>>
>

Re: [VOTE] Release Apache Iceberg 1.9.1 RC1

[Steven Wu]

+1 (binding)

Checked signature, checksum, and licenses.
"./gradlew build" passed with the source bundle.
Ran Flink 1.20 with SQL

On Fri, May 23, 2025 at 10:42 AM Russell Spitzer 
wrote:

> Discussion was back here -
> https://lists.apache.org/thread/497qxkq3nfplwo27fh959zhsc2o7hkmy
>
> On Thu, May 22, 2025 at 12:09 AM Ajantha Bhat 
> wrote:
>
>> Thanks Ebihara for pointing me to the change.
>>
>> We should probably capture end user related changes in the release notes
>> (separate section).
>> I will close that issue.
>>
>> I am good with this RC. I will test and vote.
>>
>> On Thu, May 22, 2025 at 10:26 AM Yuya Ebihara <
>> yuya.ebih...@starburstdata.com> wrote:
>>
>>> Hi Ajantha,
>>>
>>> https://github.com/apache/iceberg/pull/12318 made JSON un-pretty for
>>> reduing the file size.
>>>
>>> BR,
>>> Yuya
>>>
>>> On Thu, May 22, 2025 at 1:52 PM Ajantha Bhat 
>>> wrote:
>>>
 Hi Russell,

 Just observed this change (table metadata JSON file is not formatted
 anymore)
 https://github.com/apache/iceberg/issues/13122

 If it is induced by 1.9.0, we should probably fix it and include it in
 RC?
 No functional impact.

 - Ajantha

 On Thu, May 22, 2025 at 4:49 AM Russell Spitzer <
 russell.spit...@gmail.com> wrote:

> Hi Y'all,
>
> I propose that we release the following RC as the official Apache
> Iceberg 1.9.1 release.
>
> The commit ID is f40208ae6fb2f33e578c2637d3dea1db18739f31
> * This corresponds to the tag: apache-iceberg-1.9.1-rc1
> * https://github.com/apache/iceberg/commits/apache-iceberg-1.9.1-rc1
> *
> https://github.com/apache/iceberg/tree/f40208ae6fb2f33e578c2637d3dea1db18739f31
>
> The release tarball, signature, and checksums are here:
> *
> https://dist.apache.org/repos/dist/dev/iceberg/apache-iceberg-1.9.1-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-1202/
>
> Please download, verify, and test.
>
> Please vote in the next 72 hours.
>
> [ ] +1 Release this as Apache Iceberg 1.9.1
> [ ] +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.
>
> ---
>
> For those watching the big change between this and RC0 was the
> reversion of code which
> caused the rest client to emit multiple Snapshot Removals Requests in
> the same MetadataUpdate.
> This restores the behavior to that of 1.8.X, 1 removal per update.
> We plan to move to the new behavior in a later release
>

Re: [VOTE] Release Apache Iceberg 1.9.1 RC1

[Russell Spitzer]

Discussion was back here -
https://lists.apache.org/thread/497qxkq3nfplwo27fh959zhsc2o7hkmy

On Thu, May 22, 2025 at 12:09 AM Ajantha Bhat  wrote:

> Thanks Ebihara for pointing me to the change.
>
> We should probably capture end user related changes in the release notes
> (separate section).
> I will close that issue.
>
> I am good with this RC. I will test and vote.
>
> On Thu, May 22, 2025 at 10:26 AM Yuya Ebihara <
> yuya.ebih...@starburstdata.com> wrote:
>
>> Hi Ajantha,
>>
>> https://github.com/apache/iceberg/pull/12318 made JSON un-pretty for
>> reduing the file size.
>>
>> BR,
>> Yuya
>>
>> On Thu, May 22, 2025 at 1:52 PM Ajantha Bhat 
>> wrote:
>>
>>> Hi Russell,
>>>
>>> Just observed this change (table metadata JSON file is not formatted
>>> anymore)
>>> https://github.com/apache/iceberg/issues/13122
>>>
>>> If it is induced by 1.9.0, we should probably fix it and include it in
>>> RC?
>>> No functional impact.
>>>
>>> - Ajantha
>>>
>>> On Thu, May 22, 2025 at 4:49 AM Russell Spitzer <
>>> russell.spit...@gmail.com> wrote:
>>>
 Hi Y'all,

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

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

 The release tarball, signature, and checksums are here:
 *
 https://dist.apache.org/repos/dist/dev/iceberg/apache-iceberg-1.9.1-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-1202/

 Please download, verify, and test.

 Please vote in the next 72 hours.

 [ ] +1 Release this as Apache Iceberg 1.9.1
 [ ] +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.

 ---

 For those watching the big change between this and RC0 was the
 reversion of code which
 caused the rest client to emit multiple Snapshot Removals Requests in
 the same MetadataUpdate.
 This restores the behavior to that of 1.8.X, 1 removal per update.
 We plan to move to the new behavior in a later release

>>>

Re: [VOTE] Release Apache Iceberg 1.9.1 RC1

[Ajantha Bhat]

Thanks Ebihara for pointing me to the change.

We should probably capture end user related changes in the release notes
(separate section).
I will close that issue.

I am good with this RC. I will test and vote.

On Thu, May 22, 2025 at 10:26 AM Yuya Ebihara <
yuya.ebih...@starburstdata.com> wrote:

> Hi Ajantha,
>
> https://github.com/apache/iceberg/pull/12318 made JSON un-pretty for
> reduing the file size.
>
> BR,
> Yuya
>
> On Thu, May 22, 2025 at 1:52 PM Ajantha Bhat 
> wrote:
>
>> Hi Russell,
>>
>> Just observed this change (table metadata JSON file is not formatted
>> anymore)
>> https://github.com/apache/iceberg/issues/13122
>>
>> If it is induced by 1.9.0, we should probably fix it and include it in
>> RC?
>> No functional impact.
>>
>> - Ajantha
>>
>> On Thu, May 22, 2025 at 4:49 AM Russell Spitzer <
>> russell.spit...@gmail.com> wrote:
>>
>>> Hi Y'all,
>>>
>>> I propose that we release the following RC as the official Apache
>>> Iceberg 1.9.1 release.
>>>
>>> The commit ID is f40208ae6fb2f33e578c2637d3dea1db18739f31
>>> * This corresponds to the tag: apache-iceberg-1.9.1-rc1
>>> * https://github.com/apache/iceberg/commits/apache-iceberg-1.9.1-rc1
>>> *
>>> https://github.com/apache/iceberg/tree/f40208ae6fb2f33e578c2637d3dea1db18739f31
>>>
>>> The release tarball, signature, and checksums are here:
>>> *
>>> https://dist.apache.org/repos/dist/dev/iceberg/apache-iceberg-1.9.1-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-1202/
>>>
>>> Please download, verify, and test.
>>>
>>> Please vote in the next 72 hours.
>>>
>>> [ ] +1 Release this as Apache Iceberg 1.9.1
>>> [ ] +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.
>>>
>>> ---
>>>
>>> For those watching the big change between this and RC0 was the reversion
>>> of code which
>>> caused the rest client to emit multiple Snapshot Removals Requests in
>>> the same MetadataUpdate.
>>> This restores the behavior to that of 1.8.X, 1 removal per update.
>>> We plan to move to the new behavior in a later release
>>>
>>

Re: [VOTE] Release Apache Iceberg 1.9.1 RC1

[Yuya Ebihara]

Hi Ajantha,

https://github.com/apache/iceberg/pull/12318 made JSON un-pretty for
reduing the file size.

BR,
Yuya

On Thu, May 22, 2025 at 1:52 PM Ajantha Bhat  wrote:

> Hi Russell,
>
> Just observed this change (table metadata JSON file is not formatted
> anymore)
> https://github.com/apache/iceberg/issues/13122
>
> If it is induced by 1.9.0, we should probably fix it and include it in RC?
> No functional impact.
>
> - Ajantha
>
> On Thu, May 22, 2025 at 4:49 AM Russell Spitzer 
> wrote:
>
>> Hi Y'all,
>>
>> I propose that we release the following RC as the official Apache Iceberg
>> 1.9.1 release.
>>
>> The commit ID is f40208ae6fb2f33e578c2637d3dea1db18739f31
>> * This corresponds to the tag: apache-iceberg-1.9.1-rc1
>> * https://github.com/apache/iceberg/commits/apache-iceberg-1.9.1-rc1
>> *
>> https://github.com/apache/iceberg/tree/f40208ae6fb2f33e578c2637d3dea1db18739f31
>>
>> The release tarball, signature, and checksums are here:
>> * https://dist.apache.org/repos/dist/dev/iceberg/apache-iceberg-1.9.1-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-1202/
>>
>> Please download, verify, and test.
>>
>> Please vote in the next 72 hours.
>>
>> [ ] +1 Release this as Apache Iceberg 1.9.1
>> [ ] +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.
>>
>> ---
>>
>> For those watching the big change between this and RC0 was the reversion
>> of code which
>> caused the rest client to emit multiple Snapshot Removals Requests in the
>> same MetadataUpdate.
>> This restores the behavior to that of 1.8.X, 1 removal per update.
>> We plan to move to the new behavior in a later release
>>
>

Re: [VOTE] Release Apache Iceberg 1.9.1 RC1

[Ajantha Bhat]

Hi Russell,

Just observed this change (table metadata JSON file is not formatted
anymore)
https://github.com/apache/iceberg/issues/13122

If it is induced by 1.9.0, we should probably fix it and include it in RC?
No functional impact.

- Ajantha

On Thu, May 22, 2025 at 4:49 AM Russell Spitzer 
wrote:

> Hi Y'all,
>
> I propose that we release the following RC as the official Apache Iceberg
> 1.9.1 release.
>
> The commit ID is f40208ae6fb2f33e578c2637d3dea1db18739f31
> * This corresponds to the tag: apache-iceberg-1.9.1-rc1
> * https://github.com/apache/iceberg/commits/apache-iceberg-1.9.1-rc1
> *
> https://github.com/apache/iceberg/tree/f40208ae6fb2f33e578c2637d3dea1db18739f31
>
> The release tarball, signature, and checksums are here:
> * https://dist.apache.org/repos/dist/dev/iceberg/apache-iceberg-1.9.1-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-1202/
>
> Please download, verify, and test.
>
> Please vote in the next 72 hours.
>
> [ ] +1 Release this as Apache Iceberg 1.9.1
> [ ] +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.
>
> ---
>
> For those watching the big change between this and RC0 was the reversion
> of code which
> caused the rest client to emit multiple Snapshot Removals Requests in the
> same MetadataUpdate.
> This restores the behavior to that of 1.8.X, 1 removal per update.
> We plan to move to the new behavior in a later release
>