Re: [VOTE] Release Apache PyIceberg 0.5.0

[Hussein Awala]

+1 (non binding) I ran the example notebooks and tested some queries
with PyArrow and Pandas

On Tue, Sep 5, 2023 at 9:21 PM Fokko Driesprong  wrote:

> Hi everyone
>
> I propose that we release the following RC as the official PyIceberg 0.5.0
> release.
>
> The commit ID is 5bd7c649e4743a61eace5f52517db9b5b56ff8e6
>
> * This corresponds to the tag: pyiceberg-0.5.0rc1 (
> 4f314fc507dec4ae918d3a3dfba567a28f92ac22)
> * https://github.com/apache/iceberg/releases/tag/pyiceberg-0.5.0rc1
> *
> https://github.com/apache/iceberg/tree/5bd7c649e4743a61eace5f52517db9b5b56ff8e6
>
> The release tarball, signature, and checksums are here:
>
> * https://dist.apache.org/repos/dist/dev/iceberg/pyiceberg-0.5.0rc1/
>
> You can find the KEYS file here:
>
> * https://dist.apache.org/repos/dist/dev/iceberg/KEYS
>
> Convenience binary artifacts are staged on pypi:
>
> https://pypi.org/project/pyiceberg/0.5.0rc1/
>
> And can be installed using: pip3 install pyiceberg==0.5.0rc1
>
> Since a lot has changed due to the release of the wheels (binary Python
> libraries), I've included the following steps to verify the release
> :
>
> curl https://dist.apache.org/repos/dist/dev/iceberg/KEYS -o KEYS
> gpg --import KEYS
>
> svn checkout
> https://dist.apache.org/repos/dist/dev/iceberg/pyiceberg-0.5.0rc1/
> /tmp/pyiceberg/
>
> for name in $(ls /tmp/pyiceberg/pyiceberg-*.whl
> /tmp/pyiceberg/pyiceberg-*.tar.gz)
> do
> gpg --verify ${name}.asc ${name}
> done
>
> cd  /tmp/pyiceberg/
> for name in $(ls /tmp/pyiceberg/pyiceberg-*.whl.asc.sha512
> /tmp/pyiceberg/pyiceberg-*.tar.gz.asc.sha512)
> do
> shasum -a 512 --check ${name}
> done
>
> tar xzf pyiceberg-0.5.0.tar.gz
> cd pyiceberg-0.5.0
>
> ./dev/check-license
>
> Please download, verify, and test.
>
> Please vote in the next 72 hours.
> [ ] +1 Release this as PyIceberg 0.5.0
> [ ] +0
> [ ] -1 Do not release this because...
>
> Consider this my +1 (binding), I've tested the license, and checksums and
> ran example notebooks against the 0.5.0 rc1
> .
>
> Cheers, Fokko
>

Re: Migration of PyIceberg to iceberg-python repository

[Hussein Awala]

+1

I checked the discussion thread, and one of the motivations for this
separation was to avoid triggering unrelated CI jobs after each change.
However, I wonder if it isn't (and will not be) necessary to check the
compatibility between the main repository and the client after each change.
Otherwise, we will need to trigger the CI across the different repositories
using the GHA API, not necessarily to block the PR, but just to give quick
feedback and notification that something needs to be changed on the client
side.

On Fri, Sep 29, 2023 at 9:39 PM Brian Olsen  wrote:

> +1
>
> Great work Fokko!
>
> Pucheng,
>
> We still want to maintain all of the issues in the Python repository. The
> one thing we will lose is pull requests, but I assume there are very few.
>
> On Fri, Sep 29, 2023 at 10:34 AM Pucheng Yang 
> wrote:
>
>> Thanks for doing this. I wonder how do we deal with all the issues filed
>> for python module but still open in iceberg repo?
>>
>> On Fri, Sep 29, 2023 at 7:55 AM Eduard Tudenhoefner 
>> wrote:
>>
>>> +1 on moving to a separate repo and maintaining git history
>>>
>>> On Fri, Sep 29, 2023 at 3:30 PM Jean-Baptiste Onofré 
>>> wrote:
>>>
 Awesome, it looks even better ;)

 Thanks !
 Regards
 JB

 On Fri, Sep 29, 2023 at 2:31 PM Fokko Driesprong 
 wrote:
 >
 > Hey Ajantha,
 >
 > That's a great suggestion. I've followed the steps and created a new
 PR here: https://github.com/apache/iceberg-python/pull/3
 >
 > The subdirectory-filter command moves a subdirectory to the root
 directory. This way I still had to add some files afterward (.github/*,
 .gitignore, etc.), these are in a separate commit. Please take a look.
 >
 > Thanks,
 >
 > Fokko
 >
 > Op vr 29 sep 2023 om 13:39 schreef Ajantha Bhat <
 ajanthab...@gmail.com>:
 >>
 >> I think we are gonna lose the history of commits if we merge the
 above PR.
 >>
 >> There are ways to move the subfolder into a new repo by retaining
 commit history.
 >> For example:
 >> -
 https://medium.com/@ayushya/move-directory-from-one-repository-to-another-preserving-git-history-d210fa049d4b
 >> - https://gist.github.com/trongthanh/2779392
 >>
 >> Please give it a try.
 >>
 >> Thanks,
 >> Ajantha
 >>
 >> On Fri, Sep 29, 2023 at 4:55 PM Fokko Driesprong 
 wrote:
 >>>
 >>> Hey everyone 👋
 >>>
 >>> A while ago we discussed that Rust and Go are going into a separate
 repository:
 https://lists.apache.org/thread/4s02lmwf1kyrxxdpj3q9w2fqnxq2llbn
 >>>
 >>> Since we just did the PyIcerg 0.5.0 release, I think it is a good
 moment to migrate PyIceberg to iceberg-python as well:
 https://github.com/apache/iceberg-python/pull/2 I went over the PRs
 that are ready to merge and got them in. If there is anything missing,
 please let me know.
 >>>
 >>> I would suggest merging the PR and leaving the source code in the
 main repository for another week or so to make sure that we didn't miss
 anything.
 >>>
 >>> Since PyIceberg now also hosts the docs on the Github pages of the
 Iceberg repository, moving PyIceberg will also free up the Github pages for
 the migration of the docs back into the main repository.
 >>>
 >>> Let me know if there are any concerns.
 >>>
 >>> Kind regards,
 >>> Fokko Driesprong

>>>

Re: [VOTE] Release Apache Iceberg 1.4.0 RC1

[Hussein Awala]

+1 (non-binding) I tested it with Spark 3.3, all looks good.

On Sat, Sep 30, 2023 at 3:48 PM Jean-Baptiste Onofré 
wrote:

> Hi Anton,
>
> Yeah, I saw the addition in PR 8682. Thanks for that !
>
> Sure, I will check and also add in my "manual tests" (iceberg-samples
> repo I'm working on, preparing Icekube as manual test platform).
>
> Thanks !
> Regards
> JB
>
> On Sat, Sep 30, 2023 at 7:42 AM Anton Okolnychyi 
> wrote:
> >
> > JB, we do have tests for converting filters as well as for checking
> actual pushdown. Looks like we initially missed decimals but I've added
> them in PR 8682.
> >
> > The more tests we have the better. If you have a bit of time, it would
> be nice to go back and check what else we missed. I'd start by looking at
> TestSparkV2Filter and TestFilterPushdown classes.
> >
> > On 2023/09/30 04:56:07 Jean-Baptiste Onofré wrote:
> > > Thanks Anton,
> > >
> > > Do we have unit tests about filter pushdown ? Maybe worth to add
> > > something around that right ?
> > >
> > > Anyway, I'm adding filter test cases in my "samples" repo.
> > >
> > > Thanks !
> > > Regards
> > > JB
> > >
> > > On Fri, Sep 29, 2023 at 6:30 PM Anton Okolnychyi <
> aokolnyc...@apache.org> wrote:
> > > >
> > > > Ugh, it looks like the filter pushdown issue is a regression. I
> tested 1.3.1 and it worked. I guess it is because we migrated to V2 filters
> and their behavior is different. I need to take a closer look.
> > > >
> > > > On 2023/09/29 11:36:09 Eduard Tudenhoefner wrote:
> > > > > +1 (non-binding)
> > > > >
> > > > > * validated checksum and signature
> > > > > * checked license docs & ran RAT checks
> > > > > * ran build and tests with JDK17
> > > > > * ran some tests with Spark 3.4 + 3.5 and the new
> iceberg-aws-bundle.jar
> > > > > * ran some internal tests
> > > > >
> > > > > I found two test issues with Flink (#8680
> > > > >  and #8679
> > > > > ) while running
> tests
> > > > > locally, but that shouldn't block the release.
> > > > >
> > > > > Also thanks to Anton for doing the release and everyone else who
> > > > > contributed!
> > > > >
> > > > > On Fri, Sep 29, 2023 at 11:44 AM Fokko Driesprong <
> fo...@apache.org> wrote:
> > > > >
> > > > > > +1 (binding)
> > > > > >
> > > > > > Thanks Anton for running the release and everyone who
> contributed! Checks
> > > > > > I did:
> > > > > >
> > > > > >- Updated the docker-spark-iceberg repo
> > > > > >,
> and
> > > > > >everything runs fine (still with Spark 3.4 since there were
> some problems
> > > > > >with Jupyters' Scala 2.13 kernel). This includes new new
> aws-bundle 🥳
> > > > > >- Tested against Trino <
> https://github.com/trinodb/trino/pull/19188>,
> > > > > >and found three differences, but expected:
> > > > > >   - More defensive cleaning up of files on a failed commit,
> to make
> > > > > >   table recovery easier when needed.
> > > > > >   - A new property that's set on the table, indicating zstd
> > > > > >   compression.
> > > > > >   - Changes in the exceptions when binding a transform to a
> column
> > > > > >   type that is not allowed.
> > > > > >
> > > > > > Kind regards, Fokko
> > > > > >
> > > > > >
> > > > > > Op vr 29 sep 2023 om 07:35 schreef Jean-Baptiste Onofré <
> j...@nanthrax.net>:
> > > > > >
> > > > > >> +1 (non binding)
> > > > > >>
> > > > > >> I checked:
> > > > > >> - signatures and hash are ok
> > > > > >> - asf headers are present
> > > > > >> - no binary in the source distribution
> > > > > >> - build is ok
> > > > > >>
> > > > > >> NB: I’m working on a set of use cases with different data sets
> but it’s
> > > > > >> not yet complete. I should have it for next release and be able
> to compare
> > > > > >> queries time and behavior between releases.
> > > > > >>
> > > > > >> Thanks !
> > > > > >> Regards
> > > > > >> JB
> > > > > >>
> > > > > >> Le jeu. 28 sept. 2023 à 04:02, Anton Okolnychyi
> > > > > >>  a écrit :
> > > > > >>
> > > > > >>> Hi Everyone,
> > > > > >>>
> > > > > >>> I propose that we release the following RC as the official
> Apache
> > > > > >>> Iceberg 1.4.0 release.
> > > > > >>>
> > > > > >>> The commit ID is 8f37faa6a21e863551b17992370edc0f8706465d
> > > > > >>> * This corresponds to the tag: apache-iceberg-1.4.0-rc1
> > > > > >>> *
> https://github.com/apache/iceberg/commits/apache-iceberg-1.4.0-rc1
> > > > > >>> *
> > > > > >>>
> https://github.com/apache/iceberg/tree/8f37faa6a21e863551b17992370edc0f8706465d
> > > > > >>>
> > > > > >>> The release tarball, signature, and checksums are here:
> > > > > >>> *
> > > > > >>>
> https://dist.apache.org/repos/dist/dev/iceberg/apache-iceberg-1.4.0-rc1
> > > > > >>>
> > > > > >>> You can find the KEYS file here:
> > > > > >>> * https://dist.apache.org/repos/dist/dev/iceberg/KEYS
> > > > > >>>
> > > > > >>> Convenience binary artifacts are staged on 

Re: [VOTE] Release Apache Iceberg 1.4.0 RC2

[Hussein Awala]

+1 (non-binding) I tested it with Spark 3.3, all looks good.

On Sat, Sep 30, 2023 at 9:04 PM Bryan Keller  wrote:

> +1 (non-binding)
>
> I reran the TPC-DS benchmark with RC2, with the same setup as with RC1,
> and there were no warnings about decimal pushdown, so that appears
> resolved. The results were also a bit better at 4915 sec.
>
> -Bryan
>
> On Fri, Sep 29, 2023 at 10:37 PM Anton Okolnychyi 
> wrote:
>
>> +1 (binding)
>>
>> Validated signature, checksum, local build + tests.
>>
>> - Anton
>>
>> On 2023/09/30 04:58:15 Jean-Baptiste Onofré wrote:
>> > +1 (non binding)
>> >
>> > As for RC1, I checked:
>> > - signature and hash are OK
>> > - ASF headers are there
>> > - source distribution doesn't contain binary
>> > - build is OK
>> >
>> > Thanks,
>> > Regards
>> > JB
>> >
>> > On Sat, Sep 30, 2023 at 1:25 AM Anton Okolnychyi
>> >  wrote:
>> > >
>> > > Hi Everyone,
>> > >
>> > > I propose that we release the following RC as the official Apache
>> Iceberg 1.4.0 release.
>> > >
>> > > The commit ID is 10367c380098c2e06a49521a33681ac7f6c64b2c
>> > > * This corresponds to the tag: apache-iceberg-1.4.0-rc2
>> > > * https://github.com/apache/iceberg/commits/apache-iceberg-1.4.0-rc2
>> > > *
>> https://github.com/apache/iceberg/tree/10367c380098c2e06a49521a33681ac7f6c64b2c
>> > >
>> > > The release tarball, signature, and checksums are here:
>> > > *
>> https://dist.apache.org/repos/dist/dev/iceberg/apache-iceberg-1.4.0-rc2
>> > >
>> > > You can find the KEYS file here:
>> > > * https://dist.apache.org/repos/dist/dev/iceberg/KEYS
>> > >
>> > > Convenience binary artifacts are staged on Nexus. The Maven
>> repository URL is:
>> > > *
>> https://repository.apache.org/content/repositories/orgapacheiceberg-1146/
>> > >
>> > > Please download, verify, and test.
>> > >
>> > > Please vote in the next 72 hours. (Weekends excluded)
>> > >
>> > > [ ] +1 Release this as Apache Iceberg 1.4.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.
>> > >
>> > > - Anton
>> > >
>> >
>>
>

Re: [DISCUSSION] Rename master branch as main for the main repository

[Hussein Awala]

+1

On Mon, Oct 2, 2023 at 11:27 PM Anton Okolnychyi 
wrote:

> +1
>
> On 2023/10/02 20:12:37 Bryan Keller wrote:
> > Hearty +1 from me
> >
> >
> >
> > > On Sep 29, 2023, at 5:37 AM, Brian Olsen 
> wrote:
> > >
> > >
> >
> > > 
> > >
> > > +1000
> > >
> > >
> > >
> > >
> > > Let me know how I can help!
> > >
> > >
> > >
> > >
> > > On Fri, Sep 29, 2023 at 7:35 AM Jean-Baptiste Onofré
> > > <[j...@nanthrax.net](mailto:j...@nanthrax.net)> wrote:
> > >
> > >
> >
> > >> Hi guys,
> > >
> > >  The Apache CoC ()
>
> > >  especially contains section 5 about the wording we use. Several
> Apache
> > >  projects renamed the master branch to the main branch (Apache Karaf,
> > >  ActiveMQ, Airflow, ...).
> > >  As we already use main for go, rust, and python repositories, I
> wonder
> > >  (for consistency) if we should not rename master to main on the
> "main"
> > >  repository.
> > >
> > >  Apache INFRA can do this "smoothly" but we would have to do some
> changes:
> > >  \- update build.gradle
> > >  \- update README.md
> > >  \- update to GH Actions (in .github/workflows/*)
> > >
> > >  Thoughts ?
> > >
> > >  Regards
> > >  JB
> > >
> >
> >
>

Re: [VOTE] Release Apache Iceberg 1.4.1 RC0

[Hussein Awala]

+1 (non-binding) I tested the RC with spark 3.3 and hive catalog, and all
looks good.

On Thu, Oct 19, 2023 at 10:32 PM Steve Zhang
 wrote:

> +1 (non-binding)
>
> - validated checksum and signature
> - checked license docs & ran RAT checks
> - ran build and tests using JDK17 (problem with TestS3RestSigner
> and ADLSFileIOTest related but I think it’s setup related)
>
> Thanks,
> Steve Zhang
>
>
>
> On Oct 19, 2023, at 4:23 AM, Ajantha Bhat  wrote:
>
> +1 (non-binding)
>
> - validated checksum and signature
> - checked license docs & ran RAT checks
> - ran build and tests with JDK11
>
> Thanks,
> Ajantha
>
> On Thu, Oct 19, 2023 at 3:12 PM Xuanwo  wrote:
>
>> > Xuanwo, if you want to learn more about voting, there is also an Apache
>> page on it
>> 
>> (that includes some suggestions :). But also feel welcome to ask on the
>> devlist here.
>>
>> Thanks for pointing out the docs address. Just learnt that vote is [-1,
>> 1] instead of {-1, 0, 1}.
>>
>> On Thu, Oct 19, 2023, at 17:30, Fokko Driesprong wrote:
>>
>> Thanks Eduard for running this release!
>>
>> +1 (binding):
>>
>>- Checked the sha/signature
>>- Ran our example notebooks against 1.4.1
>> and it
>>looks well
>>
>> Xuanwo, if you want to learn more about voting, there is also an Apache
>> page on it
>> 
>> (that includes some suggestions :). But also feel welcome to ask on the
>> devlist here.
>>
>> Kind regards,
>> Fokko
>>
>>
>> Op do 19 okt 2023 om 11:02 schreef Xuanwo :
>>
>>
>> That said, from a community standpoint, it's good to take any -1 (binding
>> or non binding) into account.
>>
>> In your case, I would have voted -0 (to avoid confusion).
>>
>>
>> Lesson learned. Next time, if the same situation occurs, I'll vote -0 to
>> make my statement more clear.
>>
>> On Thu, Oct 19, 2023, at 16:23, Jean-Baptiste Onofré wrote:
>>
>> By the way, at Apache, it's not really possible to veto or block a
>> release: you need three binding votes, even if we have a fourth binding
>> vote with -1, the release can pass.
>> That said, from a community standpoint, it's good to take any -1 (binding
>> or non binding) into account.
>>
>> In your case, I would have voted -0 (to avoid confusion).
>>
>> You can see that I voted +1 because:
>> - the release is the same as the previous ones
>> - the issues have been identified and so we can fix it
>>
>> Regards
>> JB
>>
>> On Thu, Oct 19, 2023 at 10:15 AM Xuanwo  wrote:
>>
>>
>> You can see it’s what I mentioned in my vote email. However, as it’s like
>> this for a while, I voted +1 and I have PRs ready to be submitted
>> (including rat execution).
>>
>> So do you think it’s blocking ?
>>
>>
>> Thanks for the clarification.
>>
>> I'm voting -1 due to the reasons mentioned, but it doesn't block this
>> release (especially since it's non-binding). This release can proceed once
>> it garners enough +1 votes. My -1 vote is simply to highlight areas we
>> could improve in future releases.
>>
>>
>> On Thu, Oct 19, 2023, at 13:11, Jean-Baptiste Onofré wrote:
>>
>> Hi
>>
>> You can see it’s what I mentioned in my vote email. However, as it’s like
>> this for a while, I voted +1 and I have PRs ready to be submitted
>> (including rat execution).
>>
>> So do you think it’s blocking ?
>>
>> Regards
>> JB
>>
>> Le mer. 18 oct. 2023 à 16:27, Xuanwo  a écrit :
>>
>>
>> -1 (non-binding)
>>
>> - checksum and signature is good
>>
>> - the following files not have license
>>   - .baseline/idea/intellij-java-palantir-style.xml
>>   - .baseline/checkstyle/checkstyle.xml
>>   - gradle/libs.versions.toml
>>   - .baseline/checkstyle/checkstyle-suppressions.xml
>>   - .baseline/checkstyle/checkstyle-suppressions.xml
>>
>> - release contains binary files
>>   -
>> core/src/test/resources/org/apache/iceberg/puffin/v1/empty-puffin-uncompressed.bin
>>   -
>> core/src/test/resources/org/apache/iceberg/puffin/v1/sample-metric-data-compressed-zstd.bin
>>   -
>> core/src/test/resources/org/apache/iceberg/puffin/v1/sample-metric-data-uncompressed.bin
>>
>> On Wed, Oct 18, 2023, at 21:55, Eduard Tudenhoefner wrote:
>>
>> +1 (non-binding)
>>
>> * validated checksum and signature
>> * checked license docs & ran RAT checks
>> * ran build and tests with JDK8
>> * ran into one test failure, which is reported in
>> https://github.com/apache/iceberg/issues/8824, but this shouldn't block
>> the release
>> * tested with Trino in https://github.com/trinodb/trino/pull/19434
>>
>> On Wed, Oct 18, 2023 at 3:15 PM Jean-Baptiste Onofré 
>> wrote:
>>
>> +1 (non binding)
>>
>> I checked:
>> * hashes and signatures are OK
>> * I did quick tests using spark 3.5
>>
>> I found the following issues that we should fix:
>> * the source distribution contains two binary files (used for
>> tests, empty-puffin-uncompressed.bin
>> and sa

Re: [VOTE] Release Apache PyIceberg 0.5.1 RC2

[Hussein Awala]

+1 (non-binding) I ran the example notebooks and tested some queries
with PyArrow and Pandas, all looks good.

On Fri, Oct 27, 2023 at 11:46 AM Jean-Baptiste Onofré 
wrote:

> +1 (non binding)
>
> I checked:
> - hash and signatures are good
> - I will check NOTICE (copyright is 2022 and I think some deps are
> missing there), not release blocker
> - ASF headers are present
> - no binary file detected
> - very quick test
>
> Regards
> JB
>
> On Tue, Oct 24, 2023 at 8:48 PM Fokko Driesprong  wrote:
> >
> > Hi Everyone,
> >
> > I propose that we release the following RC as the official PyIceberg
> 0.5.1 release.
> >
> > This is a patch release due to bugs:
> >
> > - Part of the expression is ignored when multiple and/or expressions are
> specified
> > - Update like statements to reflect sql behaviors
> >
> > That has been found. Smaller bugs also have been backported.
> >
> > The commit ID is 891b4c7f4214fb9118080ce2215a210a770a5019
> >
> > * This corresponds to the tag: pyiceberg-0.5.1rc2
> (c5085159079fe100b7fbd38b5037d1408525dc46)
> > *
> https://github.com/apache/iceberg-python/releases/tag/pyiceberg-0.5.1rc2
> > *
> https://github.com/apache/iceberg-python/tree/891b4c7f4214fb9118080ce2215a210a770a5019
> >
> > The release tarball, signature, and checksums are here:
> >
> > * https://dist.apache.org/repos/dist/dev/iceberg/pyiceberg-0.5.1rc2/
> >
> > You can find the KEYS file here:
> >
> > * https://dist.apache.org/repos/dist/dev/iceberg/KEYS
> >
> > Convenience binary artifacts are staged on pypi:
> >
> > https://pypi.org/project/pyiceberg/0.5.1rc2/
> >
> > And can be installed using: pip3 install pyiceberg==0.5.1rc2
> >
> > Please download, verify, and test.
> >
> > Please vote in the next 72 hours.
> > [ ] +1 Release this as PyIceberg 0.5.1
> > [ ] +0
> > [ ] -1 Do not release this because...
> >
> > Consider this mail my +1 vote (binding) after running against our
> example notebooks.
> >
> > Kind regards, Fokko
>

Re: [VOTE] Release Apache Iceberg 1.4.2 RC0

[Hussein Awala]

+1 (non-binding) I tested the RC with spark 3.3 and hive catalog. All looks
good.


On Mon 30 Oct 2023 at 16:48, Eduard Tudenhoefner  wrote:

> +1 (non-binding)
>
> * validated checksum and signature
> * checked license
> * ran build and tests with JDK11
>
> On Sat, Oct 28, 2023 at 11:09 PM Amogh Jahagirdar 
> wrote:
>
>> Hi Everyone,
>>
>> I propose that we release the following RC as the official Apache Iceberg
>> 1.4.2 release.
>>
>> The commit ID is f6bb9173b13424d77e7ad8439b5ef9627e530cb2
>> * This corresponds to the tag: apache-iceberg-1.4.2-rc0
>> * https://github.com/apache/iceberg/commits/apache-iceberg-1.4.2-rc0
>> *
>> https://github.com/apache/iceberg/tree/f6bb9173b13424d77e7ad8439b5ef9627e530cb2
>>
>> The release tarball, signature, and checksums are here:
>> * https://dist.apache.org/repos/dist/dev/iceberg/apache-iceberg-1.4.2-rc0
>>
>> You can find the KEYS file here:
>> * https://dist.apache.org/repos/dist/dev/iceberg/KEYS
>>
>> Convenience binary artifacts are staged on Nexus. The Maven repository
>> URL is:
>> * https://repository.apache.org/
>> 
>> content/repositories/
>> org
>> apache iceberg-1148
>> 
>>
>> This release includes a patch for ensuring engines can successfully read
>> tables when their split offset metadata was corrupted due to a bug in
>> 1.4.0. See https://github.com/apache/iceberg/pull/8925 for more details.
>>
>> Please download, verify, and test.
>>
>> Please vote in the next 72 hours.
>> [ ] +1 Release this as Apache Iceberg 1.4.2
>> [ ] +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: [ANNOUNCE] New committer: Honah J.

[Hussein Awala]

Congrats Honah!

On Fri 12 Jan 2024 at 22:23, Micah Kornfield  wrote:

> Congrats!
>
> On Friday, January 12, 2024, Jack Ye  wrote:
>
>> Congratulations! Thanks for all the work in python!
>>
>> Best,
>> Jack Ye
>>
>> On Fri, Jan 12, 2024 at 1:11 PM Fokko Driesprong 
>> wrote:
>>
>>> On behalf of the Iceberg PMC, I'm happy to announce that Honah has
>>> accepted an invitation to become a committer on Apache (Py)Iceberg.
>>> Welcome, and thank you for your contributions!
>>>
>>> Kind regards,
>>> Fokko
>>>
>>

Re: [VOTE] Release Apache PyIceberg 0.6.0rc6

[Hussein Awala]

+1 (non-binding)

- Tested the new writing feature with a non-partitioned table
- Created a non-partitioned table using PyArrow Schema
- Tested the new MacOS arm wheel

All looks good!

On Mon, Feb 19, 2024 at 1:20 AM Honah J.  wrote:

> +1 (non-binding)
>
> - Verified signatures and checksums
> - Verified license
> - Ran unit tests and integration tests
>
> Best regards,
> Honah
>
> On Sun, Feb 18, 2024 at 2:54 PM Daniel Weeks 
> wrote:
>
>> +1 (binding)
>>
>> Verified sigs/sums/license/tests (python 3.11)
>>
>> Also ran local tests against Hive and REST catalogs using
>> appends/overwrites.
>>
>> -Dan
>>
>> On Sun, Feb 18, 2024 at 1:37 PM Ryan Blue  wrote:
>>
>>> +1 (binding)
>>>
>>> * Checked checksum, signature, recent license changes
>>> * Built and tested in Python 3.10
>>> * Ran CLI checks against a REST catalog
>>>
>>> Ryan
>>>
>>> On Thu, Feb 15, 2024 at 7:55 AM Uwe L. Korn  wrote:
>>>
 Hello all,

 just wanted to give a heads-up that I started publishing the release
 candidates on a separate channel on conda-forge:
 https://github.com/conda-forge/pyiceberg-feedstock/tree/rc. Thus, if
 you want to test them out with conda/micromamba, you can get them also via

 conda -c conda-forge/label/pyiceberg_rc install pyiceberg

 or

 micromamba -c conda-forge/label/pyiceberg_rc install pyiceberg

 Best,
 Uwe

 On Wed, Feb 14, 2024, at 3:16 PM, Sung Yun (BLOOMBERG/ 120 PARK) wrote:

 Hi Everyone,

 We are moving onto the next RC with some important fixes. This RC
 includes:

 * Bug Fix in passing configuration through environment variables #423
 * Arm wheels #416
 * Correction to the NOTICE and LICENSE #413

 Again, here's a summary of the high level features included in this
 release:

 * Write support for writing to unpartitioned tables
 * Includes snapshot generation
 * Constructing Avro writer trees
 * Support writing metadata which allows to commit support for the Hive,
 Sql, and Glue catalog.
 * Support for name-mapping
 * Easy evolution of schema using the union_by_name method
 * Support for creating unpartitioned tables using PyArrow Schema

 The commit ID is cc449266e7fe0e97f23e61b3c732b75a0d0a8dec

 * This corresponds to the tag: pyiceberg-0.6.0rc6
 (a6cf17c301561595f7cfa497a1df1ec49e682a3b)
 *
 https://github.com/apache/iceberg-python/releases/tag/pyiceberg-0.6.0rc6
 *
 https://github.com/apache/iceberg-python/tree/cc449266e7fe0e97f23e61b3c732b75a0d0a8dec

 The release tarball, signature, and checksums are here:

 * https://dist.apache.org/repos/dist/dev/iceberg/pyiceberg-0.6.0rc6/

 You can find the KEYS file here:

 * https://dist.apache.org/repos/dist/dev/iceberg/KEYS

 Convenience binary artifacts are staged on pypi:

 https://pypi.org/project/pyiceberg/0.6.0rc6/

 And can be installed using: pip3 install pyiceberg==0.6.0rc6

 Please download, verify, and test.

 Please vote in the next 72 hours.
 [ ] +1 Release this as PyIceberg 0.6.0
 [ ] +0
 [ ] -1 Do not release this because...



>>>
>>> --
>>> Ryan Blue
>>> Tabular
>>>
>>

Re: New committer: Bryan Keller

[Hussein Awala]

Congrats Bryan!

On Tue, Mar 5, 2024 at 9:20 AM Fokko Driesprong  wrote:

> Hi everyone,
>
> The Project Management Committee (PMC) for Apache Iceberg has invited
> Bryan Keller to become a committer and we are pleased to announce that he
> has accepted.
>
> Bryan was contributing to Iceberg before it was even open-source, did a
> lot of work on the topic of metadata generation, and is now leading the
> effort of migrating the Kafka Connect integration into OSS Iceberg.
>
> Being a committer enables easier contribution to the project since there
> is no need to go via the patch submission process. This should enable
> better productivity. A PMC member helps manage and guide the direction of
> the project.
>
> Please join me in congratulating Bryan.
>
> Cheers,
> Fokko
>

Re: [VOTE] Release Apache Iceberg 1.5.0 RC6

[Hussein Awala]

+1 (non-binding)
- checked checksum and signature
- built from source with jdk11
- tested read and write with Spark 3.5.1 and Glue catalog

All looks good

On Thu, Mar 7, 2024 at 10:49 PM Drew  wrote:

> +1 (non-binding)
>
> - verified signature and checksum
> - verified RAT license check
> - verified build/tests passing with JDK17
> - ran some manual tests on Spark3.5 with GlueCatalog
>
> Drew
>
> On Thu, Mar 7, 2024 at 4:38 AM Ajantha Bhat  wrote:
>
>> +1 (non-binding)
>>
>> * validated checksum and signature
>> * checked license docs & ran RAT checks
>> * ran build and tests with JDK11
>> * *verified view support for Nessie catalog with Spark 3.5.*
>> * *verified this RC against Trino
>> (https://github.com/trinodb/trino/pull/20957
>> )*
>>
>> - Ajantha
>>
>>
>> On Wed, Mar 6, 2024 at 7:25 PM Jean-Baptiste Onofré 
>> wrote:
>>
>>> +1 (non binding)
>>>
>>> - checksums and signatures are OK
>>> - ASF headers are present
>>> - No unexpected binary files in the source distribution
>>> - Build OK with JDK11
>>> - JdbcCatalog tested on Trino and Iceland
>>> - No unexpected artifact distributed
>>>
>>> Thanks !
>>>
>>> Regards
>>> JB
>>>
>>> On Wed, Mar 6, 2024 at 12:04 AM Ajantha Bhat 
>>> wrote:
>>> >
>>> > Hi Everyone,
>>> >
>>> > I propose that we release the following RC as the official Apache
>>> Iceberg 1.5.0 release.
>>> >
>>> > The commit ID is 2519ab43d654927802cc02e19c917ce90e8e0265
>>> > * This corresponds to the tag: apache-iceberg-1.5.0-rc6
>>> > * https://github.com/apache/iceberg/commits/apache-iceberg-1.5.0-rc6
>>> > *
>>> https://github.com/apache/iceberg/tree/2519ab43d654927802cc02e19c917ce90e8e0265
>>> >
>>> > The release tarball, signature, and checksums are here:
>>> > *
>>> https://dist.apache.org/repos/dist/dev/iceberg/apache-iceberg-1.5.0-rc6
>>> >
>>> > You can find the KEYS file here:
>>> > * https://dist.apache.org/repos/dist/dev/iceberg/KEYS
>>> >
>>> > Convenience binary artifacts are staged on Nexus. The Maven repository
>>> URL is:
>>> > *
>>> https://repository.apache.org/content/repositories/orgapacheiceberg-1161/
>>> >
>>> > Please download, verify, and test.
>>> >
>>> > Please vote in the next 72 hours.
>>> >
>>> > [ ] +1 Release this as Apache Iceberg 1.5.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.
>>> >
>>> > - Ajantha
>>>
>>

Re: New committer: Renjie Liu

[Hussein Awala]

Congrats Renjie!

On Sat, Mar 9, 2024 at 8:55 PM Yufei Gu  wrote:

> Congratulations and thanks for the great work in rust iceberg, Renjie!
>
> Yufei
>
>
> On Sat, Mar 9, 2024 at 11:39 AM Steven Wu  wrote:
>
>> Congrats, Renjie!
>>
>> On Sat, Mar 9, 2024 at 7:18 AM himadri pal  wrote:
>>
>>> Congratulations Renjie.
>>>
>>> Regards,
>>> Himadri Pal
>>>
>>>
>>> On Fri, Mar 8, 2024 at 11:56 PM Fokko Driesprong 
>>> wrote:
>>>
 Hi everyone,

 The Project Management Committee (PMC) for Apache Iceberg has invited
 Renjie Liu to become a committer and we are pleased to announce that he has
 accepted. We're very excited to have Renjie as a committer as he's leading
 the effort of bringing Iceberg to the Rust world.

 Being a committer enables easier contribution to the project since
 there is no need to go via the patch submission process. This should enable
 better productivity. A PMC member helps manage and guide the direction of
 the project.

 Please join me in congratulating Renjie.

 Cheers,
 Fokko

>>>

Re: [VOTE] Release Apache PyIceberg 0.6.1rc1

[Hussein Awala]

+1 (non-binding)

- Verified signatures, checksums, and license
- Tested creating and reading a non-partitioned table with the Glue catalog

On Fri, Apr 5, 2024 at 12:44 AM Justin Mclean 
wrote:

> HI,
>
> Thanks for that. I don't understand "we don't bundle the code, but just
> took some part of it”. Either the code is in the source release or not in
> the source release; if any part of it is in the source release, then it is
> bundled. The LICENSE and NOTICE files need to relate to what is included in
> the release artefact. Looking at both those PRs, it seems in both cases,
> you do bundle code, but I understand why you might not want to mention th
> autogenerated code. Either way, I think a little more is needed here to
> make the NOTICE file in line with ASF policy.
>
> Kind Regards,
> Justin

Re: [VOTE] Release Apache PyIceberg 0.6.1rc3

[Hussein Awala]

+1 (non-binding)

- checked signatures, checksums and licences
- tested writing and querying a table with Glue and Hive catalogs

On Saturday, April 20, 2024, Daniel Weeks  wrote:

> +1 (binding)
>
> Verified sigs/sums/license/tests
>
> Also manually verified the docutil dependency issues, the hive catalog
> timestamptz issue and v1 metadata issue.
>
> All looks great!
>
> I also made a small docs PR
>  to improve the
> verification process since there's a specific version hard-coded in the
> docs that we wouldn't want someone to accidentally use to verify the wrong
> version.
>
> -Dan
>
>
>
> On Thu, Apr 18, 2024 at 2:59 PM Kevin Liu  wrote:
>
>> +1 nonbinding
>> - Checked the signatures, checksums, and licenses.
>> - Ran tests (`make test`, `make test-integration`)
>>
>> I also found this page to be very helpful in learning how to verify a
>> release
>> https://py.iceberg.apache.org/verify-release/
>>
>> Best,
>> Kevin Liu
>>
>>
>> On Thu, Apr 18, 2024 at 4:14 AM Fokko Driesprong 
>> wrote:
>>
>>> Thanks Honah for the quick follow-up with RC3.
>>>
>>> +1 binding
>>>
>>> - Ran 
>>> the signatures, checksums, and licenses.
>>> - Double-checked
>>>  that
>>> it installs from a clean Python 3.10 docker-container (the abovementioned
>>> docutils issue)
>>> - Ran some simple checks
>>>  against
>>> example notebooks
>>>
>>> Kind regards,
>>> Fokko
>>>
>>> Op do 18 apr 2024 om 09:23 schreef Honah J. :
>>>
 Hi Everyone,

 I propose that we release the following RC as the official PyIceberg
 0.6.1 release.

 This is a patch release due to the following bugs:

- Fail to create version 1 table with non-empty partition-spec and
sort-order 
- Hive Catalog cannot create table with TimestamptzType field

- Fail to read parquet file with special characters in column names

- Hive Catalog commit consistency issue

- docutils=0.21 installation issue


 Smaller bugs also have been backported
 .

 The commit ID is 910dd783f16280b46704dd9679a4d003fb8a2e18

 * This corresponds to the tag: pyiceberg-0.6.1rc3 (
 876a9fb3963ab0dc80485dedfee7cee2f4a8dd13)
 * https://github.com/apache/iceberg-python/releases/tag/
 pyiceberg-0.6.1rc3
 * https://github.com/apache/iceberg-python/tree/
 910dd783f16280b46704dd9679a4d003fb8a2e18

 The release tarball, signature, and checksums are here:

 * https://dist.apache.org/repos/dist/dev/iceberg/pyiceberg-0.6.1rc3/

 You can find the KEYS file here:

 * https://dist.apache.org/repos/dist/dev/iceberg/KEYS

 Convenience binary artifacts are staged on pypi:

 https://pypi.org/project/pyiceberg/0.6.1rc3/

 And can be installed using: pip3 install pyiceberg==0.6.1rc3

 Please download, verify, and test.

 Please vote in the next 72 hours.
 [ ] +1 Release this as PyIceberg 0.6.1
 [ ] +0
 [ ] -1 Do not release this because...

>>>

Re: [VOTE] Release Apache Iceberg 1.5.1 RC0

[Hussein Awala]

+1 (non-binding)
- checked signatures, checksums and licences
- tested with Spark 3.5.1 and Glue and Hive catalogs

On Sunday, April 21, 2024, Jean-Baptiste Onofré  wrote:

> +1 (non binding)
>
> I checked the fixes on JDBC Catzlog.
>
> Regards
> JB
>
> Le ven. 19 avr. 2024 à 01:07, Amogh Jahagirdar  a
> écrit :
>
>> Hi Everyone,
>>
>> I propose that we release the following RC as the official Apache Iceberg
>> 1.5.1 release.
>>
>> The commit ID is cbb853073e681b4075d7c8707610dceecbee3a82
>> * This corresponds to the tag: apache-iceberg-1.5.1-rc0
>> * https://github.com/apache/iceberg/commits/apache-iceberg-1.5.1-rc0
>> * https://github.com/apache/iceberg/tree/cbb853073e681b4075d7c8707610dc
>> eecbee3a82
>>
>> The release tarball, signature, and checksums are here:
>> * https://dist.apache.org/repos/dist/dev/iceberg/apache-iceberg-1.5.1-rc0
>>
>> You can find the KEYS file here:
>> * https://dist.apache.org/repos/dist/dev/iceberg/KEYS
>>
>> Convenience binary artifacts are staged on Nexus. The Maven repository
>> URL is:
>> * https://repository.apache.org/
>> 
>> content/repositories/
>> 
>> orgapacheiceberg-1162/
>> 
>>
>> Please download, verify, and test.
>>
>> Please vote in the next 72 hours.
>>
>> [ ] +1 Release this as Apache Iceberg 1.5.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.
>>
>

Re: [VOTE] Release Apache Iceberg 1.6.1 RC2

[Hussein Awala]

+1 (non-binding)

Tested it in Voodoo Lakehouse unit tests with JDK 11, Spark 3.5.1, S3FileIO
(MinIO), and Hive metastore, all operations (table creation, append,
replace, overwrite partitions, merge into) work as expected.

On Tue, Aug 27, 2024 at 7:36 AM Ajantha Bhat  wrote:

> +1 (non-binding)
>
> * validated checksum and signature
> * checked license docs & ran RAT checks
> * ran build and tests with JDK11
>
> - Ajantha
>
> On Tue, Aug 27, 2024 at 9:21 AM Amogh Jahagirdar <2am...@gmail.com> wrote:
>
>> +1 (binding)
>>
>> Verified signatures, checksums, RAT checks. Ran build and tests with
>> JDK11.
>>
>> Thanks,
>>
>> Amogh Jahagirdar
>>
>> On Mon, Aug 26, 2024 at 6:21 AM Renjie Liu 
>> wrote:
>>
>>> +1 (binding)
>>>
>>> - Verified signatures, checksums
>>> - Ran `./gradlew build` and all tests passed, jdk 17
>>>
>>> On Sun, Aug 25, 2024 at 1:52 AM Fokko Driesprong 
>>> wrote:
>>>
 +1 (binding)

 - Verified signatures, checksums and ran the tests locally

 Kind regards,
 Fokko

 Op vr 23 aug 2024 om 20:51 schreef Piotr Findeisen <
 piotr.findei...@gmail.com>:

> +1 (non-binding)
>
> Trino integration
>
> https://github.com/trinodb/trino/actions/runs/10529992246/job/29179087096?pr=23083
>
> https://github.com/trinodb/trino/actions/runs/10529992246/job/29179401378?pr=23083
>
>
>
> On Fri, 23 Aug 2024 at 15:19, Eduard Tudenhöfner <
> etudenhoef...@apache.org> wrote:
>
>> +1 (binding)
>>
>> - verified signatures/checksums/license/tests
>>
>>
>>
>> On Thu, Aug 22, 2024 at 8:08 PM Carl Steinbach 
>> wrote:
>>
>>> Hi Everyone,
>>>
>>> I propose that we release the following RC as the official Apache
>>> Iceberg 1.6.1 release.
>>>
>>> The commit ID is 8e9d59d299be42b0bca9461457cd1e95dbaad086
>>> * This corresponds to the tag: apache-iceberg-1.6.1-rc2
>>> * https://github.com/apache/iceberg/commits/apache-iceberg-1.6.1-rc2
>>> *
>>> https://github.com/apache/iceberg/tree/8e9d59d299be42b0bca9461457cd1e95dbaad086
>>>
>>> The release tarball, signature, and checksums are here:
>>> *
>>> https://dist.apache.org/repos/dist/dev/iceberg/apache-iceberg-1.6.1-rc2
>>>
>>> You can find the KEYS file here:
>>> * https://dist.apache.org/repos/dist/dev/iceberg/KEYS
>>>
>>> Convenience binary artifacts are staged on Nexus. The Maven
>>> repository URL is:
>>> *
>>> https://repository.apache.org/content/repositories/orgapacheiceberg-1171/
>>>
>>> This release includes the following changes:
>>>
>>> 8e9d59d29 Build: Bump orc from 1.9.3 to 1.9.4 (#10728) (#10988)
>>> ed53c6d32 Drop ParallelIterable's queue low water mark (#10979)
>>> e18a2fe10 Core: Limit ParallelIterable memory consumption by
>>> yielding in tasks (backport #10691) (#10787)
>>>
>>> Please download, verify, and test.
>>>
>>> Please vote in the next 72 hours.
>>>
>>> [ ] +1 Release this as Apache Iceberg 1.6.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.
>>>
>>

Re: [VOTE] Deprecate and remove last-column-id

[Hussein Awala]

+1 (non-binding)

On Wednesday, November 20, 2024, Daniel Weeks  wrote:

> +1
>
> On Wed, Nov 20, 2024, 9:41 AM Aihua Xu  wrote:
>
>> +1 non-binding.
>>
>> Thanks for driving this.
>>
>> On Tue, Nov 19, 2024 at 5:50 PM Renjie Liu 
>> wrote:
>>
>>> +1, thanks Fokko!
>>>
>>> On Wed, Nov 20, 2024 at 8:45 AM Steve Zhang 
>>> 
>>> wrote:
>>>
 +1 nb

 Thanks,
 Steve Zhang



 On Nov 19, 2024, at 12:18 AM, Fokko Driesprong 
 wrote:

 Hi everyone,

 Based on the positive feedback on the [DISCUSS] thread
  and
 the pull-request on GitHub
 , I would like to raise
 a vote to deprecate and remove the last-column-id field from the spec.
 Since this is a spec change, please vote in the next 72 hours:

 [ ] +1, commit the proposed spec changes
 [ ] 0
 [ ] -1, do not make these changes because...

 Kind regards,
 Fokko

Re: [DISCUSS] Iceberg 1.7.1 release

[Hussein Awala]

Hi Bryan,

I think https://github.com/apache/iceberg/pull/11609 should also be
released in 1.7.1 as it fixes a bug in Kafka Connect introduced in 1.7.0 by
https://github.com/apache/iceberg/pull/11220.

Hussein

On Thu, Nov 21, 2024 at 3:22 AM Yufei Gu  wrote:

> Hi Bryan,
>
> This bug fix has been merged. Thanks for taking this in.
>
> Fix changelog table bug for start time older than current snapshot:
> https://github.com/apache/iceberg/pull/11564.
>
> Yufei
>
>
> On Fri, Nov 15, 2024 at 9:17 AM Aihua Xu 
> wrote:
>
>> That makes sense. Originally I thought wasb scheme change was a feature
>> change. I will wait for 1.8.0. then.
>>
>> On Fri, Nov 15, 2024 at 7:18 AM Bryan Keller  wrote:
>>
>>> I agree, we should leave this one for 1.8.
>>> -Bryan
>>>
>>> On Nov 14, 2024, at 9:22 PM, Aihua Xu 
>>> wrote:
>>>
>>> Hi Bryan,
>>>
>>> I would like to include the following in 1.7.1 if possible. I keep the
>>> change minimum and I will try to get this merged soon.
>>>
>>> Add Variant data type to API:
>>> https://github.com/apache/iceberg/pull/11324
>>>
>>> Thanks,
>>> Aihua
>>>
>>> On Thu, Nov 14, 2024 at 11:21 AM Bryan Keller  wrote:
>>>
 Hi all,

 As discussed in the sync meeting, we're planning on a fast-follow 1.7.1
 release with a few fixes and enhancements:

 Support for wasb scheme in ADLSFileIO:
 https://github.com/apache/iceberg/pull/11504

 Fix dependencies included in Kafka Connect distribution:
 https://github.com/apache/iceberg/pull/11516

 Fix nested namespace encoding in REST catalog:
 https://github.com/apache/iceberg/issues/11539

 If there are any other issues you want to include, we can discuss that
 and you can add it to the GitHub milestone.

 Thanks,
 Bryan


>>>

Re: [VOTE] Simplify multi-arg table metadata

[Hussein Awala]

+1 (non-binding)

On Sun, Feb 9, 2025 at 6:15 PM Matt Topol  wrote:

> +1 (non-binding)
>
> Will definitely make it easier for iceberg-go to support v3 :)
>
> On Sun, Feb 9, 2025, 12:14 PM Szehon Ho  wrote:
>
>> +1 (binding)
>>
>> Thanks Fokko!
>> Szehon
>>
>> > On Feb 9, 2025, at 8:14 AM, Jean-Baptiste Onofré 
>> wrote:
>> >
>> > +1 (non binding)
>> >
>> > Thanks to the cat :)
>> >
>> > Regards
>> > JB
>> >
>> >> On Sun, Feb 9, 2025 at 10:01 AM Fokko Driesprong 
>> wrote:
>> >>
>> >> (Second attempt, the cat ran over the keyboard)
>> >>
>> >> Hey everyone,
>> >>
>> >> After the positive responses on the devlist, I would like to raise a
>> vote to simplify the multi-argument transforms metadata and make it
>> exclusive for V3+ tables. The corresponding PR can be found here.
>> >>
>> >> This vote will be open for at least 72 hours.
>> >>
>> >> [ ] +1 Update the metadata to remove multi-arg transforms for V1 and
>> V2 tables
>> >> [ ] +0
>> >> [ ] -1 I have questions and/or concerns
>> >>
>> >> Kind regards,
>> >> Fokko
>> >>
>> >> Op zo 9 feb 2025 om 09:57 schreef Driesprong, Fokko
>> :
>> >>>
>> >>> Hey everyone,
>> >>>
>> >>> After the positive responses on the devlist, I would like to raise a
>> vote to simplify the multi-argument transforms metadata, and make it
>> exclusve
>> >>>
>> >>> A vote to simplify the
>>
>

Re: [VOTE] Release Apache Iceberg 1.7.2 rc0

[Hussein Awala]

Hi folks,

Is there any intention to proceed with the release or is it completely
cancelled?

Regards,
Hussein

On Wednesday, January 29, 2025, Jean-Baptiste Onofré 
wrote:

> Hi folks,
>
> in order to merge the LICENSE/NOTICE improvement on our binary
> artifacts, I cancel this vote for rc0.
>
> As soon as the PRs will be merged, I will propose rc1 to vote.
>
> Regards
> JB
>
> On Sun, Jan 26, 2025 at 9:41 PM Jean-Baptiste Onofré 
> wrote:
> >
> > Hi everyone,
> >
> > I propose that we release the following RC as the official Apache
> > Iceberg 1.7.2 release.
> >
> > The commit ID is c2105b2634becf68b3fdabd0ee6fb0b6e93d4f0c
> > * This corresponds to the tag: apache-iceberg-1.7.2-rc0
> > * https://github.com/apache/iceberg/commits/apache-iceberg-1.7.2-rc0
> > * https://github.com/apache/iceberg/tree/c2105b2634becf68b3fdabd0ee6fb0
> b6e93d4f0c
> >
> > The release tarball, signature, and checksums are here:
> > * https://dist.apache.org/repos/dist/dev/iceberg/apache-
> iceberg-1.7.2-rc0
> >
> > 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-1180/
> >
> > For the changes, checkout the Milestone:
> > https://github.com/apache/iceberg/milestone/52?closed=1
> >
> > Please download, verify, and test. Please vote in the next 72 hours.
> >
> > [ ] +1 Release this as Apache Iceberg 1.7.2
> > [ ] +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.
> >
> > Thanks,
> > Regards
> > JB & Fokko
>

Re: [VOTE] Release Apache Iceberg 1.7.2 rc0

[Hussein Awala]

> Do you still need 1.7.2 or 1.8.0/1.8.1 is good enough for you ?

If 1.8.1 will be released soon, that would be great. We prefer not to use
the first release for a minor version in production and wait for at least a
patch release, but 1.7.X is completely broken.


On Thu, Feb 20, 2025 at 8:30 AM Eduard Tudenhöfner 
wrote:

> I think we should still do 1.7.2 and not leave it in a broken state.
>
> On Thu, Feb 20, 2025 at 7:56 AM Jean-Baptiste Onofré 
> wrote:
>
>> Hi Hussein
>>
>> We were focusing on 1.8.x.
>>
>> Do you still need 1.7.2 or 1.8.0/1.8.1 is good enough for you ?
>>
>> Regards
>> JB
>>
>> On Wed, Feb 19, 2025 at 10:23 PM Hussein Awala  wrote:
>> >
>> > Hi folks,
>> >
>> > Is there any intention to proceed with the release or is it completely
>> cancelled?
>> >
>> > Regards,
>> > Hussein
>> >
>> > On Wednesday, January 29, 2025, Jean-Baptiste Onofré 
>> wrote:
>> >>
>> >> Hi folks,
>> >>
>> >> in order to merge the LICENSE/NOTICE improvement on our binary
>> >> artifacts, I cancel this vote for rc0.
>> >>
>> >> As soon as the PRs will be merged, I will propose rc1 to vote.
>> >>
>> >> Regards
>> >> JB
>> >>
>> >> On Sun, Jan 26, 2025 at 9:41 PM Jean-Baptiste Onofré 
>> wrote:
>> >> >
>> >> > Hi everyone,
>> >> >
>> >> > I propose that we release the following RC as the official Apache
>> >> > Iceberg 1.7.2 release.
>> >> >
>> >> > The commit ID is c2105b2634becf68b3fdabd0ee6fb0b6e93d4f0c
>> >> > * This corresponds to the tag: apache-iceberg-1.7.2-rc0
>> >> > * https://github.com/apache/iceberg/commits/apache-iceberg-1.7.2-rc0
>> >> > *
>> https://github.com/apache/iceberg/tree/c2105b2634becf68b3fdabd0ee6fb0b6e93d4f0c
>> >> >
>> >> > The release tarball, signature, and checksums are here:
>> >> > *
>> https://dist.apache.org/repos/dist/dev/iceberg/apache-iceberg-1.7.2-rc0
>> >> >
>> >> > 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-1180/
>> >> >
>> >> > For the changes, checkout the Milestone:
>> >> > https://github.com/apache/iceberg/milestone/52?closed=1
>> >> >
>> >> > Please download, verify, and test. Please vote in the next 72 hours.
>> >> >
>> >> > [ ] +1 Release this as Apache Iceberg 1.7.2
>> >> > [ ] +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.
>> >> >
>> >> > Thanks,
>> >> > Regards
>> >> > JB & Fokko
>>
>

Re: [VOTE] Release Apache Iceberg 1.8.1 RC1

[Hussein Awala]

+1 (non-binding) - Tested with Spark 3.5.4, JDK 17, S3 FileIO (MinIO), and
Hive3 as the catalog.
Validated the following operations:
- Creating a new table
- Appending data
- Merging into tables
- Updating schema and properties
- Scanning tables

On Mon, Feb 24, 2025 at 2:49 PM Eduard Tudenhoefner 
wrote:

> Hi Everyone,
>
> I propose that we release the following RC as the official Apache Iceberg
> 1.8.1 release.
>
> The commit ID is *9ce0fcf0af7becf25ad9fc996c3bad2afdcfd33d*
> * This corresponds to the tag: *apache-iceberg-1.8.1-rc1*
> * https://github.com/apache/iceberg/commits/apache-iceberg-1.8.1-rc1
> *
> https://github.com/apache/iceberg/tree/9ce0fcf0af7becf25ad9fc996c3bad2afdcfd33d
>
> The release tarball, signature, and checksums are here:
> * https://dist.apache.org/repos/dist/dev/iceberg/apache-iceberg-1.8.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-1184/
>
> Please download, verify, and test.
>
> Please vote in the next 72 hours.
>
> [ ] +1 Release this as Apache Iceberg 1.8.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.
>
>

Re: [VOTE] Release Apache PyIceberg 0.9.0rc3

[Hussein Awala]

Hi Drew,

It seems that the pyiceberg-0.9.0 tag has not been created, nor the release
which should contain the release note:
https://py.iceberg.apache.org/how-to-release/#post-release

Best,
Hussein

On Mon, Mar 3, 2025 at 11:45 PM Kevin Liu  wrote:

> Woot! Thanks for running the release, Drew! And thanks for verifying,
> everyone. We'll work on getting the final artifact published.
>
> Best,
> Kevin Liu
>
> On Mon, Mar 3, 2025 at 1:32 PM Drew  wrote:
>
>> Thanks everyone for voting!!
>>
>> The 72 hours have passed, and a minimum of 3 binding votes have been cast:
>> - +1: 3 (binding), 2 (non-binding)
>> - +0: 0
>> - -1: 0
>>
>> The release candidate has been officially accepted as *PyIceberg 0.9.0*.
>>
>> Thank you again for your participation! The announcement will be sent out
>> once all artifacts are published.
>>
>> Best,
>> Drew
>>
>> On Mon, Mar 3, 2025 at 9:37 AM Eduard Tudenhöfner <
>> etudenhoef...@apache.org> wrote:
>>
>>> +1 (binding)
>>>
>>> checked signatures/checksums/license and ran tests via "make
>>> test-coverage".
>>>
>>> Thanks everyone
>>>
>>> On Mon, Mar 3, 2025 at 3:10 PM Sung Yun  wrote:
>>>
 Hi Drew, thank you very much for running the release!

 +1 non-binding:

 I've verified the signatures, the checksums and the licensing.
 Ran tests with "make test-coverage"

 Sung

 On 2025/03/03 05:01:18 "Honah J." wrote:
 > Thanks Drew for running the release!
 >
 > +1 (binding)
 >
 >- Checked signatures/checksum/licenses
 >- Ran tests via "make test-coverage" on Python3.12
 >
 > Note: running tests against "getdaft>=0.4.5" will get some errors as
 > recorded in https://github.com/apache/iceberg-python/pull/1739,
 > https://github.com/Eventual-Inc/Daft/issues/3876. I do no think this
 is a
 > release blocker, but others following the "how-to-release" guide may
 > encounter these errors until daft releases a new version contains the
 fix.
 >
 > Best regards,,
 > Honah
 >
 > On Sun, Mar 2, 2025 at 11:59 AM Fokko Driesprong 
 wrote:
 >
 > > Thanks Drew for running this release!
 > >
 > > +1 (binding)
 > >
 > > Checked checksums, signatures, and licenses and ran some tests
 locally.
 > >
 > > Kind regards,
 > > Fokko
 > >
 > >
 > >
 > > Op wo 26 feb 2025 om 22:21 schreef Kevin Liu >>> >:
 > >
 > >> +1 (non-binding)
 > >>
 > >> Following the "Verifying a release" doc
 > >> <
 https://github.com/apache/iceberg-python/blob/main/mkdocs/docs/verify-release.md
 >
 > >> .
 > >> Downloaded from SVN
 > >> ```
 > >> svn checkout
 > >> https://dist.apache.org/repos/dist/dev/iceberg/pyiceberg-0.9.0rc3
 > >> pyiceberg/
 > >> ```
 > >> Checked
 > >> * gpg: Good signature from "Drew Gallardo "
 [unknown]
 > >> * Checksum OK
 > >> * RAT checks passed. 1 extra ERROR line but is unrelated
 > >> ```
 > >> ERROR: Ignored 0 lines in your exclusion files as comments or
 empty lines.
 > >> ```
 > >> * Both unit and integration test passed with Python 3.12.8 on M1
 and
 > >> Orbstack
 > >>
 > >> Thanks for being the release manager, Drew! Third time's a charm!
 :)
 > >>
 > >> Best,
 > >> Kevin Liu
 > >>
 > >> On Wed, Feb 26, 2025 at 11:17 AM Drew  wrote:
 > >>
 > >>> Hi Everyone,
 > >>>
 > >>> I propose that we release the following RC as the official
 PyIceberg
 > >>> 0.9.0 release.
 > >>>
 > >>> A summary of the high level features:
 > >>>
 > >>>- 235 new commits
 > >>>
 > >>> *High Level Features:*
 > >>>
 > >>>- Implemented support for Alibaba OSS protocol in PyArrowFileIO
 > >>>- Enabled Dynamic Overwrite capability
 > >>>- Introduced V3 read support
 > >>>- Added support for Polars DataFrame and LazyFrame
 > >>>- Enabled column projection for efficient data access
 > >>>- Added table statistics
 > >>>- Implemented table UPSERT support with improved deduplication
 logic
 > >>>- Added support for Location Providers
 > >>>- Extended support for write paths with Location Providers
 > >>>(write.data.path, write.metadata.path)
 > >>>- Removed table name parsing from row_filter
 > >>>- Cross region S3 read support
 > >>>
 > >>> *Bug Fixes:*
 > >>>
 > >>>- Resolved issues reading from multiple S3 regions
 > >>>- Corrected URL encoding of partition field names
 > >>>- Fixed a TypeError issue with composite keys
 > >>>- Ensured proper handling of missing Parquet metadata
 > >>>
 > >>> *Documentation & Infrastructure:*
 > >>>
 > >>>- Improved contribution guidelines
 > >>>- Automated CI with nightly builds and release candidate
 processes
 > >>>- Automate building Release 

Re: [DISCUSS] Rename iceberg repo to iceberg-java ?

[Hussein Awala]

I agree with Russell that the spec should remain language-agnostic.
However, for the Java client (and other integrations implemented in
Java), +1 for moving them to a new repository. Alternatively, we could
rename the current repository and relocate the spec to a new repository
under the existing name.
The ideal time for this work could be during the development of Iceberg v2.



On Fri, Mar 14, 2025 at 8:52 PM Jean-Baptiste Onofré 
wrote:

> OK, thanks guys for your feedback.
>
> It was a more "open question" to give more "consistency" (like other
> projects did, Arrow, Parquet, etc). But definitely not strongly
> required :)
>
> Let's skip this one for now.
>
> Regards
> JB
>
> On Fri, Mar 14, 2025 at 7:29 PM Daniel Weeks  wrote:
> >
> > I'm not in favor of the rename at this point.
> >
> > This just seems unnecessary and since the java implementation is the
> reference implementation I don't think there's real confusion caused by
> leaving the repo as it is.
> >
> > I know this has been done in other projects like `parquet-mr` ->
> `parquet-java`, but that was more due to the `mr` designation being
> confusing and obsolete.
> >
> >
> > On Fri, Mar 14, 2025 at 8:58 AM Russell Spitzer <
> russell.spit...@gmail.com> wrote:
> >>
> >> I generally dislike renames unless we are going to get some tangible
> benefit out of it. Consistency
> >> is never something I really care that much about in repository names
> since no one is really using
> >> those on a daily basis and they aren't really used programmatically.
> >>
> >> If we did do this rename would we be breaking all old hyper links to
> the repo? If so, I think I'd say I'm a -1. I also
> >> find it more confusing in projects where this has happened and the
> repository is retained for old
> >> links but the README just says, go to  instead.
> >>
> >> All that said, I think iceberg-java is the right name of the java impl
> and the spec should probably be split
> >> into another repo. But that's what I would have done with perfect
> foresight before we got to the current state.
> >>
> >> So depending on the impact to existing links and references I'm between
> a -1 and +0.
> >>
> >> Things that would convince me to be a +1
> >>
> >> Frequency of how often the single repository is confusing to folks, and
> does this affect them on a daily basis?
> >> Would we be able to route all requests to the old repository
> automatically to the new one?
> >> Would impacts on current developers be minimal? How many dev setups
> need to be changed for this to work?
> >>
> >> On Fri, Mar 14, 2025 at 10:21 AM Jean-Baptiste Onofré 
> wrote:
> >>>
> >>> Hi folks,
> >>>
> >>> I know it's not an easy one, but I would like to start this discussion
> :)
> >>>
> >>> We now have several repositories:
> >>> - iceberg-cpp
> >>> - iceberg-go
> >>> - iceberg-python
> >>> - iceberg-rust
> >>>
> >>> To be consistent, what about renaming iceberg to iceberg-java ?
> >>>
> >>> I know it's not only Java (it's also specs and site), but it would be
> >>> clearer, especially for contributors and the community.
> >>>
> >>> Thoughts ?
> >>>
> >>> Regards
> >>> JB
>