Hi everyone,
I am pleased to announce that we have unanimously approved this release
candidate:
There are 14 approving votes, 3 of which are binding:
- Xintong （binding)
- Yun Tang (non-binding)
- Lijie (non-binding)
- Xingbo (non-binding)
- Leonard Xu (non-binding)
- Sergey (non-binding)
-
arge parallelism batch jobs and performance does not
> > degrade.
> > > >>
> > > >> Best,
> > > >> JunRui
> > > >>
> > > >> yuxia 于2022年10月25日周二 09:23写道：
> > > >>
> > > >>> +
; >> yuxia 于2022年10月25日周二 09:23写道：
> > >>
> > >>> +1 (non-binding)
> > >>> * Build from source
> > >>> * Use Flink Sql client create catalog/tables
> > >>> * Use Hive dialect to run some queries and insert stateme
gt; >> Best,
> >> JunRui
> >>
> >> yuxia 于2022年10月25日周二 09:23写道：
> >>
> >>> +1 (non-binding)
> >>> * Build from source
> >>> * Use Flink Sql client create catalog/tables
> >>> * Use Hive dialect to run s
>
>>> +1 (non-binding)
>>> * Build from source
>>> * Use Flink Sql client create catalog/tables
>>> * Use Hive dialect to run some queries and insert statements
>>>
>>> Best regards,
>>> Yuxia
>>>
>>> - 原始邮件 --
to run some queries and insert statements
> >
> > Best regards,
> > Yuxia
> >
> > ----- 原始邮件 -
> > 发件人: "Teoh, Hong"
> > 收件人: "dev"
> > 发送时间: 星期二, 2022年 10 月 25日 上午 4:35:39
> > 主题: Re: [VOTE] Release 1.16.0, release candidate
; * Use Hive dialect to run some queries and insert statements
>
> Best regards,
> Yuxia
>
> - 原始邮件 -
> 发件人: "Teoh, Hong"
> 收件人: "dev"
> 发送时间: 星期二, 2022年 10 月 25日 上午 4:35:39
> 主题: Re: [VOTE] Release 1.16.0, release candidate #2
>
> +1 (no
on-binding)
> > > >>>
> > > >>>
> > > >>> * build from the source code.
> > > >>> * verified the signature of the release binaries.
> > > >>> * launched a standalone cluster with
> > >>>
> > > >>>
> > > >>> * build from the source code.
> > > >>> * verified the signature of the release binaries.
> > > >>> * launched a standalone cluster with examples for both
> * The new speculative execution works as expected
> > > >>
> > > >> Best,
> > > >> Lijie
> > > >>
> > > >> Yun Tang 于2022年10月22日周六 15:20写道：
> > > >>
> > > >>> +1 (non-
>
> > >>> +1 (non-binding)
> > >>>
> > >>>
> > >>> * build from the source code.
> > >>> * verified the signature of the release binaries.
> > >>> * launched a standalone cluster with examples for both
> > >> streaming/batch
> &
gt;> * verified the signature of the release binaries.
> >>> * launched a standalone cluster with examples for both
> >> streaming/batch
> >>> execution modes.
> >>> * checked rocksdb's log would exist under Flink's default log
> folder.
> >>> *
h
>> streaming/batch
>>> execution modes.
>>> * checked rocksdb's log would exist under Flink's default log folder.
>>> * reviewed the flink-web PR
>>>
>>> Best
>>> Yun Tang
>>>
>>> From: X
t; > ____
> > From: Xintong Song
> > Sent: Friday, October 21, 2022 18:29
> > To: dev@flink.apache.org
> > Subject: Re: [VOTE] Release 1.16.0, release candidate #2
> >
> > +1 (binding) for this release candidate
> >
> > - v
d the flink-web PR
>
> Best
> Yun Tang
>
> From: Xintong Song
> Sent: Friday, October 21, 2022 18:29
> To: dev@flink.apache.org
> Subject: Re: [VOTE] Release 1.16.0, release candidate #2
>
> +1 (binding) for this release candidate
-web PR
Best
Yun Tang
From: Xintong Song
Sent: Friday, October 21, 2022 18:29
To: dev@flink.apache.org
Subject: Re: [VOTE] Release 1.16.0, release candidate #2
+1 (binding) for this release candidate
- verified checksum & signature
- build from source
- t
+1 (binding) for this release candidate
- verified checksum & signature
- build from source
- tried example jobs with standalone cluster, web ui & logs look good
- the new completed jobs & history server features work as expected
- the new hybrid shuffle mode works as expected
Best,
Xintong
+1 to make 1.16.0 released as soon as possible,
it's been more than two months since feature freeze,
1.17 already starts kicking off. We can fix the critical bugs in 1.16.1.
Best,
Godfrey
Xintong Song 于2022年10月21日周五 09:57写道：
>
> BTW, missing 1.16.0 is probably not that bad. From my experience,
BTW, missing 1.16.0 is probably not that bad. From my experience, the x.y.0
releases are usually considered unstable and are mainly for trying out
purposes. Most users do not upgrade to the new version in production until
the x.y.1/2 releases, which are considered more stable. As this bug-fix is
We had a similar situation for Flink 1.15.1 where a non-regression
"critical" bug was impacting a connector [1]. We decided to not block the
release to address this issue. Based on this, I am inclined to agree with
Martijn and move forward with the release. This bug is not marked as a
"blocker"
Taking in this fix would require us to cancel RC2 and create another
release candidate. We are already long-overdue on the Flink 1.16 release.
Given that 1.15.3 is not yet released, it can't be a regression compared to
the current situation of 1.15.2. The Flink Delta connector is not part of
the
Thank you all for response,
however i think you may miss a bigger context regarding those 3 tickets.
Those 3 tickets [29509, 29512, 29627] are part of a bigger thing. They are
fixing 1.15 Sink V2 issue, where Task manager will not start after recovery
for Sink topology with Global Committer. The
Hi Krzysztof,
When I was building rc2, I tried to search whether issues with `fix
version` of 1.16.0 have not been closed.
https://issues.apache.org/jira/browse/FLINK-29627 was missed because the
`fix version` was not marked. I agree with Martijn and Xintong that we
won't block 1.16.0 on this.
Hi Krzysztof,
FLINK-29627 is merged after rc2 being created, that's why it doesn't appear
in the change list. See the commit history of rc2 [1].
It's unfortunate this fix didn't make the 1.16.0 release (if rc2 is
approved). However, I agree with Martijn that we should not further block
1.16.0 on
Thanks Martijn,
just to clarify from my end,
All three tickets, [1] [2] [3] are fixed and merged to 1.16 branch
already. I just noticed that one of them [3] is not on included in the
change list. Hence my email.
[1] https://issues.apache.org/jira/browse/FLINK-29509
[2]
Hi Krzysztof,
Given that this issue already exists in previous Flink versions, I don't
think it's a blocker for 1.16. We should get it fixed (all of the tickets)
so it will be addressed in a new Flink 1.15 version, in Flink 1.16.1 and of
course Flink 1.17.
Best regards,
Martijn
On Thu, Oct 20,
Hi,
I would like to ask about [1] ticket with PR [2]. It was merged to 1.16
release branch today but I do not see it on the change list.
It is closely related to [3] and [4] that are on the change list. However
to fully fix Sink architecture issue we need all 3 tickets [1], [3] and [4]
[1]
Hi everyone,
Please review and vote on the release candidate #2 for the version 1.16.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],
28 matches
Mail list logo
