Hi everyone,
I'm pleased to announce that we have unanimously approved this release
candidate:
There are 13 approving votes, 4 of which are binding:
- Lijie Wang (non-binding)
- Jing Ge (non-binding)
- Yuxia Luo (non-binding)
- Martijn Visser (binding)
- Dong Lin (binding)
- Ran Tao
e tests
> > with final checkpoint disabled:
> > execution.checkpointing.checkpoints-after-tasks-finish.enabled: false
> > In the following versions we'll also try to trigger a checkpoint
> > immediately
> > after the sources finished to reduce the waiting time.
>
/FLINK-25105 <
> https://issues.apache.org/jira/browse/FLINK-25105 >
> [2] https://issues.apache.org/jira/browse/FLINK-25105 <
> https://issues.apache.org/jira/browse/FLINK-25105 >
> --
> From:Leonard Xu
&g
wse/FLINK-25105 >
[2] https://issues.apache.org/jira/browse/FLINK-25105
<https://issues.apache.org/jira/browse/FLINK-25105 >
--
From:Leonard Xu
Send Time:2023 Mar. 22 (Wed.) 18:07
To:dev
Subject:Re: [VOTE] Release 1.1
Hi, Yu Chen
> The test results show that Flink 1.17 has a significant performance
> degradation compared to Flink 1.13 (About 8.49%), shall we need to identify
> the reason for the performance degradation before Flink 1.17 is released?
Thanks for the verification, I wonder why you compared to
Hi Qingshen again,
I just did an in-depth review of the release notes as promised. I have
not opened the jira tickets though.
PTAL
Best
Etienne
Le 22/03/2023 à 08:43, Qingsheng Ren a écrit :
Hi Jakub,
Thanks for reviewing the release note and welcome to the Flink community!
We will
Hi, all.
We have built a Standalone Cluster based on Flink 1.17-RC3 release package
with 8 TMs with Nexmark[1].
The test results show that Flink 1.17 has a significant performance
degradation compared to Flink 1.13 (About 8.49%), shall we need to identify
the reason for the performance
Hi Qingsheng,
Yes indeed I was referring to the jira release notes. I know they are
generated, I was wondering if we could configure the generation process.
Anyway, the human readable release notes are clear enough. I'll review
the related PR.
Best
Etienne
Le 22/03/2023 à 09:14, Qingsheng
Hi Etienne,
Thanks for the review!
I guess you are referring to the JIRA release note [1]. I didn't find a
place to configure the format of it, as it is auto-generated by JIRA.
Actually there will be a more "human-readable" release note [1] for users
in the document, which highlights breaking
Hi Jakub,
Thanks for reviewing the release note and welcome to the Flink community!
We will change the fix version of all open issues to 1.17.1 in batch before
the final release, then these issues will disappear from the release note
auto-generated by JIRA.
Please feel free to raise any doubts
Hi,
I was looking through release notes [1], and found one the list some
tasks, that have status "Open". For example: FLINK-28538 [2], FLINK-19722
[2], FLINK-18873 [3]. Is this situation expected, or should these tasks be
removed from release notes?
This is my first message on this mailing list,
+1 (no-binding)
+ verify signatures and checksums
+ build Flink from source (from the src archive)
+ run simple job flink on k8s application mode and session cluster
Robert Metzger 于2023年3月21日周二 20:36写道：
> +1 (binding)
>
> + Started Flink locally with the changelog statebackend + rocksdb
+1 (binding)
+ Started Flink locally with the changelog statebackend + rocksdb against
minio
+ used the maven artifacts to develop a little, large-state sample job to
test with the changelog statebackend
+ Opened this PR https://github.com/apache/flink/pull/22232
+ Manually eyeballed the diff for
+1 (binding)
- verify signatures and checksums
- verify python wheel package contents
- pip install apache-flink-libraries and apache-flink wheel packages
- run example flink/flink-python/pyflink/examples/table/basic_operations.py
with Python 3.10
- reviewed release note PR
Best,
Xingbo
Sergey
+1 (non-binding)
- downloaded, checked hashes
- verified signatures
- built from sources
- checked LICENSE and NOTICE files
- ran simple jobs
On Tue, Mar 21, 2023, 11:16 Etienne Chauchot wrote:
> Hi all,
>
> - I read the release notes: I'd suggest if possible that we group the
> subtasks by
Hi all,
- I read the release notes: I'd suggest if possible that we group the
subtasks by main task and show the main tasks to give better
understanding to the reader.
- tested RC3 on a standalone cluster with this user code:
https://github.com/echauchot/tpcds-benchmark-flink
+1
_
> From: Ran Tao
> Sent: Monday, March 20, 2023 22:46
> To: dev@flink.apache.org
> Subject: Re: [VOTE] Release 1.17.0, release candidate #3
>
> +1 (non-binding)
>
> - Verified signature
> - Verified hash
> - Build the source with Apple M
the web PR
Best
Yun Tang
From: Ran Tao
Sent: Monday, March 20, 2023 22:46
To: dev@flink.apache.org
Subject: Re: [VOTE] Release 1.17.0, release candidate #3
+1 (non-binding)
- Verified signature
- Verified hash
- Build the source with Apple M1 chip.
- Run
+1 (non-binding)
- Verified signature
- Verified hash
- Build the source with Apple M1 chip.
- Run streaming and batch job in sql-client successfully.
- Build pyflink with M1 chip and run a pyflink job successfully.
- Verified web PR
Thanks Martijn and Matthias, Leonard and Qingsheng for driving
; wrote:
> >
> > > +1 (non-binding)
> > > 1: Build from the source code
> > > 2: Verified the signature and checksum
> > > 3: Verified web PR
> > > 4: Run a SQL Job via Flink SQL Client
> > >
> > > Best regards,
> > > Yu
from the source code
> > 2: Verified the signature and checksum
> > 3: Verified web PR
> > 4: Run a SQL Job via Flink SQL Client
> >
> > Best regards,
> > Yuxia
> >
> > ----- 原始邮件 -----
> > 发件人: "Leonard Xu"
> > 收件人: "dev
xia
>
> - 原始邮件 -
> 发件人: "Leonard Xu"
> 收件人: "dev"
> 发送时间: 星期一, 2023年 3 月 20日 上午 11:19:01
> 主题: Re: [VOTE] Release 1.17.0, release candidate #3
>
> Thanks Jing for the validation, I’ve created FLINK-31519[1] to fix the
> outdated doc,
> S
+1 (non-binding)
1: Build from the source code
2: Verified the signature and checksum
3: Verified web PR
4: Run a SQL Job via Flink SQL Client
Best regards,
Yuxia
- 原始邮件 -
发件人: "Leonard Xu"
收件人: "dev"
发送时间: 星期一, 2023年 3 月 20日 上午 11:19:01
主题: Re: [VOTE] Release 1.17.
Thanks Jing for the validation, I’ve created FLINK-31519[1] to fix the outdated
doc,
Sure that it’s a minor doc issue and won’t block the release.
Best,
Leonard
[1]https://issues.apache.org/jira/browse/FLINK-31519
> On Mar 20, 2023, at 7:45 AM, Jing Ge wrote:
>
> Hi Qingsheng,
>
> While
Thanks Jing for the validation!
The document doesn't block the releasing process. A GitHub action picks up
the latest commit on release branches and builds docs nightly.
Also cc'ing the author of FLINK-28853 for updating the doc.
Best,
Qingsheng
On Mon, Mar 20, 2023 at 7:46 AM Jing Ge wrote:
Hi Qingsheng,
While reviewing the announcement PR[1], I found that the related Flink doc
for Watermark Alignment Enhancement has not been updated yet. Afaiac, It is
not a blocking issue but would be great if it contains up-to-date
information and is consistent with the announcement.
Best
+1
- Verified the signature
- Verified hashes
- Verify that the source archives do not contain any binaries
- Built from the source code
- Verified web PR
- Checked jars in the staging repo
Best regards,
Jing
On Sat, Mar 18, 2023 at 9:11 AM Lijie Wang wrote:
> +1 (binding)
>
> - Built from
+1 (binding)
- Built from the source code
- Verified the signature and checksum
- Ran both streaming/batch jobs on yarn cluster
- Checked the website PR
Best,
Lijie
Qingsheng Ren 于2023年3月17日周五 22:02写道：
> Hi everyone,
>
> Please review and vote on the release candidate #3 for the
Hi everyone,
Please review and vote on the release candidate #3 for the version 1.17.0,
as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
The complete staging area is available for your review, which includes:
* JIRA release notes [1],
29 matches
Mail list logo
