[DISCUSS] Apache Iceberg 1.4.1

2023-10-16 Thread Eduard Tudenhoefner
Hi everyone,

I wanted to start a discussion to have a 1.4.1 patch release.

We discovered a critical issue with split offsets in manifests that can
result in corrupted metadata when those invalid offsets are read and then
written back. Details with a proposed fix are described in #8834
.

I've created a 1.4.1 milestone
 in GH to track any
additional fixes we'd like to get out. One particular issue that quite a
few people are running into is #8677
.

Do people have any other bug fixes that should be included?

Thanks
Eduard


Re: [DISCUSS] Apache Iceberg 1.4.1

2023-10-16 Thread Jean-Baptiste Onofré
Hi Eduard

It sounds good to me. I have some dep upgrades I think it would be
good to include (I'm working on testing/benchmark about that). Thanks
to you, we already merged the most important. I'm doing a pass now.

In terms of pure bug fix, I don't have anything in mind.

Regards
JB

On Mon, Oct 16, 2023 at 12:49 PM Eduard Tudenhoefner  wrote:
>
> Hi everyone,
>
> I wanted to start a discussion to have a 1.4.1 patch release.
>
> We discovered a critical issue with split offsets in manifests that can 
> result in corrupted metadata when those invalid offsets are read and then 
> written back. Details with a proposed fix are described in #8834.
>
> I've created a 1.4.1 milestone in GH to track any additional fixes we'd like 
> to get out. One particular issue that quite a few people are running into is 
> #8677.
>
> Do people have any other bug fixes that should be included?
>
> Thanks
> Eduard


Re: PyIceberg 0.5.1 patch release

2023-10-16 Thread Ryan Blue
Thanks, Fokko! I merged the blocker so I think we're ready for a release
candidate.

On Sun, Oct 15, 2023 at 6:30 AM Fokko Driesprong  wrote:

> Hey everyone,
>
> This week we've discovered a serious bug when parsing SQL-like string
> expressions  (thanks Pucheng
> for reporting this)! Ryan suggested doing a quick patch release to get this
> fix out to the public ASAP, and I think that's a great idea. Since it is
> just a patch release, I'm happy to run it. I've created the
> pyiceberg-0.5.x branch
> , and 
> created
> a milestone . I've
> cherry-picked 8 PRs to this branch that don't introduce any behavioral
> changes. Let me know if anything is missing.
>
> There is one PR that needs to get in
>  before I can start the
> release process.
>
> Cheers, Fokko
>


-- 
Ryan Blue
Tabular


Iceberg Slack invite

2023-10-16 Thread Lin, Jon
I’m evaluating Iceberg for my team’s transition to Open Table Formats.

Is it possible to get access to the slack workspace?  The invite 
link
 wouldn’t let me signup with my gmail account.


Re: Iceberg Slack invite

2023-10-16 Thread Fokko Driesprong
Hey Lin,

Can you try this link:
https://join.slack.com/t/apache-iceberg/shared_invite/zt-2561tq9qr-UtISlHgsdY3Virs3Z2_btQ
The
link you mentioned is working for me, but I'm already part of the
workspace. Can you share the error that you're seeing?

Kind regards,
Fokko

Op ma 16 okt 2023 om 22:39 schreef Lin, Jon :

> I’m evaluating Iceberg for my team’s transition to Open Table Formats.
>
>
>
> Is it possible to get access to the slack workspace?  The invite link
> 
> wouldn’t let me signup with my gmail account.
>


[VOTE] Release Apache PyIceberg 0.5.1 (RC1)

2023-10-16 Thread Fokko Driesprong
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 a bug that has been found
. Smaller bugs also have
been backported
.


The commit ID is ea9da8856a686eaeda0d5c2be78d5e3102b67c44


* This corresponds to the tag: pyiceberg-0.5.1rc1
(320b0f499d14178210c3b9cb7d94dab1e1b149e6)

* https://github.com/apache/iceberg-python/releases/tag/pyiceberg-0.5.1rc1

* https://github.com/apache/iceberg-python
/tree/ea9da8856a686eaeda0d5c2be78d5e3102b67c44



The release tarball, signature, and checksums are here:


* https://dist.apache.org/repos/dist/dev/iceberg/pyiceberg-0.5.1rc1/


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.1rc1/


And can be installed using: pip3 install pyiceberg==0.5.1rc1


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...


Kind regards,

Fokko


Re: [DISCUSS] Apache Iceberg 1.4.1

2023-10-16 Thread Steven Wu
Hi Eduard,

I would like to include this change/revert for the 1.4.1 patch release.
https://github.com/apache/iceberg/issues/8847

PR is not created yet. it should be a very small change in one file.

Thanks,
Steven

On Mon, Oct 16, 2023 at 6:50 AM Jean-Baptiste Onofré 
wrote:

> Hi Eduard
>
> It sounds good to me. I have some dep upgrades I think it would be
> good to include (I'm working on testing/benchmark about that). Thanks
> to you, we already merged the most important. I'm doing a pass now.
>
> In terms of pure bug fix, I don't have anything in mind.
>
> Regards
> JB
>
> On Mon, Oct 16, 2023 at 12:49 PM Eduard Tudenhoefner 
> wrote:
> >
> > Hi everyone,
> >
> > I wanted to start a discussion to have a 1.4.1 patch release.
> >
> > We discovered a critical issue with split offsets in manifests that can
> result in corrupted metadata when those invalid offsets are read and then
> written back. Details with a proposed fix are described in #8834.
> >
> > I've created a 1.4.1 milestone in GH to track any additional fixes we'd
> like to get out. One particular issue that quite a few people are running
> into is #8677.
> >
> > Do people have any other bug fixes that should be included?
> >
> > Thanks
> > Eduard
>


Re: [VOTE] Release Apache PyIceberg 0.5.1 (RC1)

2023-10-16 Thread Jean-Baptiste Onofré
+1 (non binding)

I checked:
- hash and signature are good
- source distribution is good
- run a quick test locally

Thanks,
Regards
JB

On Mon, Oct 16, 2023 at 11:28 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 a bug that has been found. Smaller bugs also 
> have been backported.
>
>
> The commit ID is ea9da8856a686eaeda0d5c2be78d5e3102b67c44
>
>
> * This corresponds to the tag: pyiceberg-0.5.1rc1 
> (320b0f499d14178210c3b9cb7d94dab1e1b149e6)
>
> * https://github.com/apache/iceberg-python/releases/tag/pyiceberg-0.5.1rc1
>
> * 
> https://github.com/apache/iceberg-python/tree/ea9da8856a686eaeda0d5c2be78d5e3102b67c44
>
>
> The release tarball, signature, and checksums are here:
>
>
> * https://dist.apache.org/repos/dist/dev/iceberg/pyiceberg-0.5.1rc1/
>
>
> 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.1rc1/
>
>
> And can be installed using: pip3 install pyiceberg==0.5.1rc1
>
>
> 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...
>
>
> Kind regards,
>
> Fokko