Re: [ANNOUNCE] Release 1.17.0, release candidate #1

2023-03-13 Thread Leonard Xu
> > The RC works on this tested scope. I'll test again on RC2. Cool, thanks for your validation,Etienne! We'll prepare the RC2 ASAP. Best, Leonard

Re: [ANNOUNCE] Release 1.17.0, release candidate #1

2023-03-13 Thread Leonard Xu
> > By the way, it seems the apache/flink-benchmarks repo did not checkout a > branch target for flink-1.17 [1] ? > Thanks Yun for reporting this, I'll check apache/flink-benchmarks repo. Best, Leonard

Re: [ANNOUNCE] Release 1.17.0, release candidate #1

2023-03-13 Thread Yun Tang
ch 13, 2023 21:49 To: dev@flink.apache.org Subject: Re: [ANNOUNCE] Release 1.17.0, release candidate #1 Hi, Thanks Martijn and release managers for this RC. I tested it in a standalone cluster on this (1) benchmark / user code [1] https://github.com/echauchot/tpcds-benchmark-flink The RC works on

Re: [ANNOUNCE] Release 1.17.0, release candidate #1

2023-03-13 Thread Etienne Chauchot
Hi, Thanks Martijn and release managers for this RC. I tested it in a standalone cluster on this (1) benchmark / user code [1] https://github.com/echauchot/tpcds-benchmark-flink The RC works on this tested scope. I'll test again on RC2. Best Etienne Le 09/03/2023 à 20:31, Martijn Visser a é

Re: [ANNOUNCE] Release 1.17.0, release candidate #1

2023-03-13 Thread Martijn Visser
Hi Yunhong, Thanks for the message. Technically this is not a release blocker for 1.17, since the issue already exists in Flink 1.16. The CI isn't passing for the PR, so it also looks like this won't be fixed soon. I've lowered the priority to a Critical ticket, but if this isn't merged in the nex

Re: [ANNOUNCE] Release 1.17.0, release candidate #1

2023-03-13 Thread yh z
Hi Qingsheng Ren and other release manager, Thank you for bringing this up. There is a serious bug in planner rule #FlinkFilterJoinRule, which will generate a wrong join plan and no result will output: https://issues.apache.org/jira/browse/FLINK-31273 (reviewing). This bug will be triggered by a

Re: [ANNOUNCE] Release 1.17.0, release candidate #1

2023-03-13 Thread Qingsheng Ren
Thanks everyone for validating the RC! As there are some patches to be included and signature issues, the RC1 of 1.17.0 is officially canceled. Because the ASF Nexus server is now in maintenance, we'll build a new RC after the server gets online, which is hopefully on Tuesday (Mar 14). Best, Qing

Re: [ANNOUNCE] Release 1.17.0, release candidate #1

2023-03-10 Thread Yingjie Cao
Hi Martijn, Thanks a lot. Fix has be merged. Best regards, Yingjie Martijn Visser 于2023年3月10日周五 03:32写道: > Hi Yingjie, > > Thanks for the test and identifying the issue, this is super helpful! > > To all others, please continue your testing on this RC so that if there are > more blockers to be

Re: [ANNOUNCE] Release 1.17.0, release candidate #1

2023-03-10 Thread Sergey Nuyanzin
I guess there is something wrong with signature while checking it i got this gpg: assuming signed data in 'flink-1.17.0-bin-scala_2.12.tgz' gpg: Signature made Wed 08 Mar 2023 03:59:17 PM CET gpg:using RSA key A1BD477F79D036D2C30CA7DBCA8AEEC2F6EB040B gpg: BAD signature from "Qingsh

Re: [ANNOUNCE] Release 1.17.0, release candidate #1

2023-03-09 Thread Martijn Visser
Hi Yingjie, Thanks for the test and identifying the issue, this is super helpful! To all others, please continue your testing on this RC so that if there are more blockers to be found, we can fix them with the next RC and have (hopefully) a successful vote on it. Best regards, Martijn On Thu,

Re: [ANNOUNCE] Release 1.17.0, release candidate #1

2023-03-09 Thread Yingjie Cao
Hi community and release managers: When testing the release candidate #1 for batch scenario, I found a potential deadlock issue of blocking shuffle. I have created a ticket [1] for it and marked it as blocker. I will fix it no later than tomorrow. [1] https://issues.apache.org/jira/browse/FLINK-3

[ANNOUNCE] Release 1.17.0, release candidate #1

2023-03-08 Thread Qingsheng Ren
Hi everyone, The RC1 for Apache Flink 1.17.0 has been created. This RC currently is for preview only to facilitate the integrated testing since the release announcement is still under review. The voting process will be triggered once the announcement is ready. It has all the artifacts that we woul