Re: Re: [VOTE] Accept Flink CDC into Apache Flink

[Xingbo Huang]

+1 (binding)

Best,
Xingbo

Dian Fu  于2024年1月10日周三 11:35写道：

> +1 (binding)
>
> Regards,
> Dian
>
> On Wed, Jan 10, 2024 at 5:09 AM Sharath  wrote:
> >
> > +1 (non-binding)
> >
> > Best,
> > Sharath
> >
> > On Tue, Jan 9, 2024 at 1:02 PM Venkata Sanath Muppalla <
> sanath...@gmail.com>
> > wrote:
> >
> > > +1 (non-binding)
> > >
> > > Thanks,
> > > Sanath
> > >
> > > On Tue, Jan 9, 2024 at 11:16 AM Peter Huang <
> huangzhenqiu0...@gmail.com>
> > > wrote:
> > >
> > > > +1 (non-binding)
> > > >
> > > >
> > > > Best Regards
> > > > Peter Huang
> > > >
> > > >
> > > > On Tue, Jan 9, 2024 at 5:26 AM Jane Chan 
> wrote:
> > > >
> > > > > +1 (non-binding)
> > > > >
> > > > > Best,
> > > > > Jane
> > > > >
> > > > > On Tue, Jan 9, 2024 at 8:41 PM Lijie Wang <
> wangdachui9...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > +1 (non-binding)
> > > > > >
> > > > > > Best,
> > > > > > Lijie
> > > > > >
> > > > > > Jiabao Sun  于2024年1月9日周二
> 19:28写道：
> > > > > >
> > > > > > > +1 (non-binding)
> > > > > > >
> > > > > > > Best,
> > > > > > > Jiabao
> > > > > > >
> > > > > > >
> > > > > > > On 2024/01/09 09:58:04 xiangyu feng wrote:
> > > > > > > > +1 (non-binding)
> > > > > > > >
> > > > > > > > Regards,
> > > > > > > > Xiangyu Feng
> > > > > > > >
> > > > > > > > Danny Cranmer  于2024年1月9日周二 17:50写道：
> > > > > > > >
> > > > > > > > > +1 (binding)
> > > > > > > > >
> > > > > > > > > Thanks,
> > > > > > > > > Danny
> > > > > > > > >
> > > > > > > > > On Tue, Jan 9, 2024 at 9:31 AM Feng Jin 
> > > wrote:
> > > > > > > > >
> > > > > > > > > > +1 (non-binding)
> > > > > > > > > >
> > > > > > > > > > Best,
> > > > > > > > > > Feng Jin
> > > > > > > > > >
> > > > > > > > > > On Tue, Jan 9, 2024 at 5:29 PM Yuxin Tan <
> ta...@gmail.com>
> > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > +1 (non-binding)
> > > > > > > > > > >
> > > > > > > > > > > Best,
> > > > > > > > > > > Yuxin
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > Márton Balassi  于2024年1月9日周二 17:25写道：
> > > > > > > > > > >
> > > > > > > > > > > > +1 (binding)
> > > > > > > > > > > >
> > > > > > > > > > > > On Tue, Jan 9, 2024 at 10:15 AM Leonard Xu <
> > > > xb...@gmail.com>
> > > > > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > > +1(binding)
> > > > > > > > > > > > >
> > > > > > > > > > > > > Best,
> > > > > > > > > > > > > Leonard
> > > > > > > > > > > > >
> > > > > > > > > > > > > > 2024年1月9日 下午5:08，Yangze Guo 
> 写道：
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > +1 (non-binding)
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Best,
> > > > > > > > > > > > > > Yangze Guo
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > On Tue, Jan 9, 2024 at 5:06 PM Robert Metzger <
> > > > > > > > > rmetz...@apache.org
> > > > > > > > > > >
> > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> +1 (binding)
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> On Tue, Jan 9, 2024 at 9:54 AM Guowei Ma <
> > > > > gu...@gmail.com
> > > > > > >
> > > > > > > > > > > > wrote:
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >>> +1 (binding)
> > > > > > > > > > > > > >>> Best,
> > > > > > > > > > > > > >>> Guowei
> > > > > > > > > > > > > >>>
> > > > > > > > > > > > > >>>
> > > > > > > > > > > > > >>> On Tue, Jan 9, 2024 at 4:49 PM Rui Fan <
> > > > > 19...@gmail.com>
> > > > > > > > > > > wrote:
> > > > > > > > > > > > > >>>
> > > > > > > > > > > > >  +1 (non-binding)
> > > > > > > > > > > > > 
> > > > > > > > > > > > >  Best,
> > > > > > > > > > > > >  Rui
> > > > > > > > > > > > > 
> > > > > > > > > > > > >  On Tue, Jan 9, 2024 at 4:41 PM Hang Ruan <
> > > > > > > > > > ruanhang1...@gmail.com>
> > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > 
> > > > > > > > > > > > > > +1 (non-binding)
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Best,
> > > > > > > > > > > > > > Hang
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > gongzhongqiang 
> 于2024年1月9日周二
> > > > > > > > > > 16:25写道：
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >> +1 non-binding
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> Best,
> > > > > > > > > > > > > >> Zhongqiang
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >> Leonard Xu  于2024年1月9日周二
> > > > 15:05写道：
> > > > > > > > > > > > > >>
> > > > > > > > > > > > > >>> Hello all,
> > > > > > > > > > > > > >>>
> > > > > > > > > > > > > >>> This is the official vote whether to
> accept the
> > > > > Flink
> > > > > > > CDC
> > > > > > > > > > code
> > > > > > > > > > > > > >> contribution
> > > > > > > > > > > > > >>> to Apache Flink.
> > > > > > > > > > > > > >>>
> > > > > > > > > > > > > >>> The current Flink CDC code, documentation,
> and
> > > > > > website
> > > > > > > can
> > > > > > > > > be
> > > > > > > > > > > > > >>> found here:
> > > > > > > > > > > 

Re: [DISCUSS] Externalized Python Connector Release/Dependency Process

[Xingbo Huang]

Hi Danny,

+1

Thanks a lot for investigating this. Let me share the current code
management and release situation of pyflink here. I hope it will be helpful
to you.

Since Flink 1.13, release managers need to release two python packages to
pypi, apache-flink[1] and apache-flink-libraries[2]. apache-flink contains
all pyflink python code and apache-flink-libraries contains the jar package
corresponding to flink binary. The reason why the content of
apache-flink-libaries is not put into apache-flink is because starting from
Flink 1.11, pyflink provides different python versions and platform wheel
packages. If all wheel packages contain these jar packages, the space of
apache-flink will quickly increase, but pypi's project space is limited(I
applied to expand apache-flink twice), so in 1.13, I move the corresponding
jar package from apache-flink to an independent apache-flink-libraries
package.

Since each apache-connector wheel package today is shared by the platform,
we do not need to publish a corresponding apache-libraries package for a
connector currently, but we still need to package the corresponding jar of
the connector into the corresponding apche-connector pypi package.

[1] https://pypi.org/project/apache-flink/
[2] https://pypi.org/project/apache-flink-libraries/

Best,
Xingbo

Leonard Xu  于2024年1月9日周二 13:46写道：

> +1
>
> Thanks Danny for driving this.
>
> Best,
> Leonard
>
>
> > 2024年1月9日 上午2:01，Márton Balassi  写道：
> >
> > +1
> >
> > Thanks, Danny - I really appreciate you taking the time for the in-depth
> > investigation. Please proceed, looking forward to your experience.
> >
> > On Mon, Jan 8, 2024 at 6:04 PM Martijn Visser 
> > wrote:
> >
> >> Thanks for investigating Danny. It looks like the best direction to go
> to
> >> :)
> >>
> >> On Mon, Jan 8, 2024 at 5:56 PM Péter Váry 
> >> wrote:
> >>>
> >>> Thanks Danny for working on this!
> >>>
> >>> It would be good to do this in a way that the different connectors
> could
> >>> reuse as much code as possible, so if possible put most of the code to
> >> the
> >>> flink connector shared utils repo [1]
> >>>
> >>> +1 from for the general direction (non-binding)
> >>>
> >>> Thanks,
> >>> Peter
> >>>
> >>> [1] https://github.com/apache/flink-connector-shared-utils
> >>>
> >>>
> >>> Danny Cranmer  ezt írta (időpont: 2024. jan.
> >> 8.,
> >>> H, 17:31):
> >>>
>  Hello all,
> 
>  I have been working with Péter and Marton on externalizing python
>  connectors [1] from the main repo to the connector repositories. We
> >> have
>  the code moved and the CI running tests for Kafka and AWS Connectors.
> >> I am
>  now looking into the release process.
> 
>  When we undertake a Flink release we perform the following steps [2],
>  regarding Python: 1/ run python build on CI, 2/ download Wheels
> >> artifacts,
>  3/ upload artifacts to the dist and 4/ deploy to pypi. The plan is to
>  follow the same steps for connectors, using Github actions instead of
> >> Azure
>  pipeline.
> 
>  Today we have a single pypi project for pyflink that contains all the
> >> Flink
>  libs, apache-flink [3]. I propose we create a new pypi project per
>  connector using the existing connector version, and following naming
>  convention: apache-, for example:
>  apache-flink-connector-aws, apache-flink-connector-kafka. Therefore to
> >> use
>  a DataStream API connector in python, users would need to first
> >> install the
>  lib, for example "python -m pip install apache-flink-connector-aws".
> 
>  Once we have consensus I will update the release process and perform a
>  release of the flink-connector-aws project to test it end-to-end. I
> >> look
>  forward to any feedback.
> 
>  Thanks,
>  Danny
> 
>  [1] https://issues.apache.org/jira/browse/FLINK-33528
>  [2]
> 
> >>
> https://cwiki.apache.org/confluence/display/FLINK/Creating+a+Flink+Release
>  [3] https://pypi.org/project/apache-flink/
> 
> >>
>
>

Re: [DISCUSS] Drop python 3.7 support in 1.19

[Xingbo Huang]

Hi Gabor,

Thanks a lot for the detailed explanation. Building a test environment with
multi-platforms is indeed what we have been lacking,
not only for M1 users, but also for Windows users. At 1.16, I remember that
Azure did not provide the m1 environment,
and the github action just planned m1 in the annual plan at that
time[1][2].

+1 for drop 3.7 support in 1.19

[1] https://github.com/actions/runner-images/issues/2187
[2] https://github.com/github/roadmap/issues/528

Best,
Xingbo

Gabor Somogyi  于2023年9月6日周三 16:07写道：

> Hi Xingbo,
>
> > So I guess you want to run ci tests  on the m1
> > environment, but the current version of miniconda cannot meet this
> > requirement, so there is a pre-step that must drop python 3.7?
>
> In short yes + local wheel build fix on the M1. In a bit more detailed
> please let me elaborate.
>
> You're right about the arm64 build creation, Flink is doing that for quite
> some time already and wheels are running fine.
> There are gaps however.
>
> From user perspective:
> * we're building wheels for ARM64 but we're not executing any python tests
> on ARM64 but only on X64.
> I think it's a must to test platform packages on the related platform since
> not all python packages are ARM compatible or must be built/used in a
> different way.
>
> From dev perspective:
> * Local MacOs M1 wheel or python source distro builds are simply failing
> with error messages.
> Just to give an example GRPC pip install is failing and require the
> following changes:
>
> https://github.com/apache/flink/pull/23359/files#diff-c4c4916cd6ab7f87a4b154ef9603f9ba6d3b74a00096be9adacb7df363b5efcfR28-R32
> I can't really imagine how Azure is able to build MacOS ARM64 wheels...
> * Python tests are not running on any kind of ARM CPUs which makes any bug
> hunting/development hard or nearly impossible
>
> In order to give ARM support with local development + test execution
> possibility new miniconda is needed. New miniconda runs 3.8+.
>
> There is already a PR which is under development:
> https://github.com/apache/flink/pull/23359
> This fills all the mentioned gaps: local test/development/test execution on
> ARM CPUs + the previously mentioned 3+ years not actively supported python
> eliminated.
>
> Hope this helps.
>
> G
>
>
> On Wed, Sep 6, 2023 at 9:00 AM Xingbo Huang  wrote:
>
> > Hi Gyala and Gabor,
> >
> > Pyflink has provided arm64 wheel packages for Apple silicon since
> 1.16[1].
> > The use of Miniconda is only related to ci testing and packaging on linux
> > platform, and building mac platform wheels are dependent on
> > cibuildwheel[2]. So I guess you want to run ci tests  on the m1
> > environment, but the current version of miniconda cannot meet this
> > requirement, so there is a pre-step that must drop python 3.7?
> >
> > [1] https://pypi.org/project/apache-flink/1.16.2/#files
> > [2]
> >
> >
> https://github.com/apache/flink/blob/master/tools/azure-pipelines/build-python-wheels.yml#L30
> >
> > Best,
> > Xingbo
> >
> > Gabor Somogyi  于2023年9月6日周三 14:36写道：
> >
> > > Hi Xingbo,
> > >
> > > *Constraint:*
> > > I personally not found any miniconda version which provides arm64
> support
> > > together with python 3.7.
> > > [image: image.png]
> > >
> > > At the moment I think new platform support means 3.7 drop.
> > >
> > > I fully to agree with Gyula, if we start now maybe we can release it in
> > > half a year however *3.7 active support already ended in 27 Jun 2020*.
> > > At the moment any python development/test execution on MacOS M1 is just
> > > not working as-is just like any kind of python test execution on any
> ARM
> > > CPU.
> > >
> > > Gains:
> > > * We can release a working version in half a year hopefully and not
> > > shifting support to 1+ year
> > > * MacOS M1 local development would work finally which is essential for
> > > user engagement
> > > * It would be possible to execute python tests on ARM64 machines
> > > * We can shake up the python development story because it's not the
> most
> > > loved area
> > >
> > > BR,
> > > G
> > >
> > >
> > > On Wed, Sep 6, 2023 at 8:06 AM Gyula Fóra 
> wrote:
> > >
> > >> Hi Xingbo!
> > >>
> > >> I think we have to analyze what we gain by dropping 3.7 and upgrading
> > to a
> > >> miniconda version with a multiarch support.
> > >>
> > >> If this is what we need to get Apple silicon support then I think it's
> >

Re: [DISCUSS] Drop python 3.7 support in 1.19

[Xingbo Huang]

Hi Gyala and Gabor,

Pyflink has provided arm64 wheel packages for Apple silicon since 1.16[1].
The use of Miniconda is only related to ci testing and packaging on linux
platform, and building mac platform wheels are dependent on
cibuildwheel[2]. So I guess you want to run ci tests  on the m1
environment, but the current version of miniconda cannot meet this
requirement, so there is a pre-step that must drop python 3.7?

[1] https://pypi.org/project/apache-flink/1.16.2/#files
[2]
https://github.com/apache/flink/blob/master/tools/azure-pipelines/build-python-wheels.yml#L30

Best,
Xingbo

Gabor Somogyi  于2023年9月6日周三 14:36写道：

> Hi Xingbo,
>
> *Constraint:*
> I personally not found any miniconda version which provides arm64 support
> together with python 3.7.
> [image: image.png]
>
> At the moment I think new platform support means 3.7 drop.
>
> I fully to agree with Gyula, if we start now maybe we can release it in
> half a year however *3.7 active support already ended in 27 Jun 2020*.
> At the moment any python development/test execution on MacOS M1 is just
> not working as-is just like any kind of python test execution on any ARM
> CPU.
>
> Gains:
> * We can release a working version in half a year hopefully and not
> shifting support to 1+ year
> * MacOS M1 local development would work finally which is essential for
> user engagement
> * It would be possible to execute python tests on ARM64 machines
> * We can shake up the python development story because it's not the most
> loved area
>
> BR,
> G
>
>
> On Wed, Sep 6, 2023 at 8:06 AM Gyula Fóra  wrote:
>
>> Hi Xingbo!
>>
>> I think we have to analyze what we gain by dropping 3.7 and upgrading to a
>> miniconda version with a multiarch support.
>>
>> If this is what we need to get Apple silicon support then I think it's
>> worth doing it already in 1.19. Keep in mind that 1.18 is not even
>> released
>> yet so if we delay this to 1.20 that is basically 1 year from now.
>> Making this change can increase the adoption instantly if we enable new
>> platforms.
>>
>> Cheers,
>> Gyula
>>
>> On Wed, Sep 6, 2023 at 4:46 AM Xingbo Huang  wrote:
>>
>> > Hi Gabor,
>> >
>> > Thanks for bringing this up. In my opinion, it is a bit aggressive to
>> > directly drop Python 3.7 in 1.19. Python 3.7 is still used a lot[1],
>> and as
>> > far as I know, many Pyflink users are still using python 3.7 as their
>> > default interpreter. I prefer to deprecate Python 3.7 in 1.19 just like
>> we
>> > deprecated Python 3.6 in 1.16[2] and dropped Python 3.6 in 1.17[3].
>> >
>> > For the support of Python 3.11, I am very supportive of the
>> implementation
>> > in 1.19 (many users have this appeal, and I originally wanted to
>> support it
>> > in 1.18).
>> >
>> > Regarding the miniconda upgrade, I tend to upgrade miniconda to the
>> latest
>> > version that can support python 3.7 to 3.11 at the same time.
>> >
>> > [1] https://w3techs.com/technologies/history_details/pl-python/3
>> > [2] https://issues.apache.org/jira/browse/FLINK-28195
>> > [3] https://issues.apache.org/jira/browse/FLINK-27929
>> >
>> > Best,
>> > Xingbo
>> >
>> > Jing Ge  于2023年9月5日周二 04:10写道：
>> >
>> > > +1
>> > >
>> > > @Dian should we add support of python 3.11
>> > >
>> > > Best regards,
>> > > Jing
>> > >
>> > > On Mon, Sep 4, 2023 at 3:39 PM Gabor Somogyi <
>> gabor.g.somo...@gmail.com>
>> > > wrote:
>> > >
>> > > > Thanks for all the responses!
>> > > >
>> > > > Based on the suggestions I've created the following jiras and
>> started
>> > to
>> > > > work on them:
>> > > > * https://issues.apache.org/jira/browse/FLINK-33029
>> > > > * https://issues.apache.org/jira/browse/FLINK-33030
>> > > >
>> > > > The reason why I've split them is to separate the concerns and
>> reduce
>> > the
>> > > > amount of code in a PR to help reviewers.
>> > > >
>> > > > BR,
>> > > > G
>> > > >
>> > > >
>> > > > On Mon, Sep 4, 2023 at 12:57 PM Sergey Nuyanzin <
>> snuyan...@gmail.com>
>> > > > wrote:
>> > > >
>> > > > > +1,
>> > > > > Thanks for looking into this.
>> > > > >
>> > > > > On Mon,

Re: [DISCUSS] Drop python 3.7 support in 1.19

[Xingbo Huang]

Hi Gabor,

Thanks for bringing this up. In my opinion, it is a bit aggressive to
directly drop Python 3.7 in 1.19. Python 3.7 is still used a lot[1], and as
far as I know, many Pyflink users are still using python 3.7 as their
default interpreter. I prefer to deprecate Python 3.7 in 1.19 just like we
deprecated Python 3.6 in 1.16[2] and dropped Python 3.6 in 1.17[3].

For the support of Python 3.11, I am very supportive of the implementation
in 1.19 (many users have this appeal, and I originally wanted to support it
in 1.18).

Regarding the miniconda upgrade, I tend to upgrade miniconda to the latest
version that can support python 3.7 to 3.11 at the same time.

[1] https://w3techs.com/technologies/history_details/pl-python/3
[2] https://issues.apache.org/jira/browse/FLINK-28195
[3] https://issues.apache.org/jira/browse/FLINK-27929

Best,
Xingbo

Jing Ge  于2023年9月5日周二 04:10写道：

> +1
>
> @Dian should we add support of python 3.11
>
> Best regards,
> Jing
>
> On Mon, Sep 4, 2023 at 3:39 PM Gabor Somogyi 
> wrote:
>
> > Thanks for all the responses!
> >
> > Based on the suggestions I've created the following jiras and started to
> > work on them:
> > * https://issues.apache.org/jira/browse/FLINK-33029
> > * https://issues.apache.org/jira/browse/FLINK-33030
> >
> > The reason why I've split them is to separate the concerns and reduce the
> > amount of code in a PR to help reviewers.
> >
> > BR,
> > G
> >
> >
> > On Mon, Sep 4, 2023 at 12:57 PM Sergey Nuyanzin 
> > wrote:
> >
> > > +1,
> > > Thanks for looking into this.
> > >
> > > On Mon, Sep 4, 2023 at 8:38 AM Gyula Fóra 
> wrote:
> > >
> > > > +1
> > > > Thanks for looking into this.
> > > >
> > > > Gyula
> > > >
> > > > On Mon, Sep 4, 2023 at 8:26 AM Matthias Pohl  > > > .invalid>
> > > > wrote:
> > > >
> > > > > Thanks Gabor for looking into it. It sounds reasonable to me as
> well.
> > > > >
> > > > > +1
> > > > >
> > > > > On Sun, Sep 3, 2023 at 5:44 PM Márton Balassi <
> > > balassi.mar...@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Hi Gabor,
> > > > > >
> > > > > > Thanks for bringing this up. Similarly to when we dropped Python
> > 3.6
> > > > due
> > > > > to
> > > > > > its end of life (and added 3.10) in Flink 1.17 [1,2], it makes
> > sense
> > > to
> > > > > > proceed to remove 3.7 and add 3.11 instead.
> > > > > >
> > > > > > +1.
> > > > > >
> > > > > > [1] https://issues.apache.org/jira/browse/FLINK-27929
> > > > > > [2] https://github.com/apache/flink/pull/21699
> > > > > >
> > > > > > Best,
> > > > > > Marton
> > > > > >
> > > > > > On Fri, Sep 1, 2023 at 10:39 AM Gabor Somogyi <
> > > > gabor.g.somo...@gmail.com
> > > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Hi All,
> > > > > > >
> > > > > > > I've analyzed through part of the pyflink code and found some
> > > > > improvement
> > > > > > > possibilities.
> > > > > > > I would like to hear voices on the idea.
> > > > > > >
> > > > > > > Intention:
> > > > > > > * upgrade several python related versions to eliminate
> > end-of-life
> > > > > issues
> > > > > > > and keep up with bugfixes
> > > > > > > * start to add python arm64 support
> > > > > > >
> > > > > > > Actual situation:
> > > > > > > * Flink supports the following python versions: 3.7, 3.8, 3.9,
> > 3.10
> > > > > > > * We use miniconda 4.7.10 (python package management system and
> > > > > > environment
> > > > > > > management system) which supports the following python
> versions:
> > > 3.7,
> > > > > > 3.8,
> > > > > > > 3.9, 3.10
> > > > > > > * Our python framework is not supporting anything but x86_64
> > > > > > >
> > > > > > > Issues:
> > > > > > > * Python 3.7.17 is the latest security patch of the 3.7 line.
> > This
> > > > > > version
> > > > > > > is end-of-life and is no longer supported:
> > > > > > > https://www.python.org/downloads/release/python-3717/
> > > > > > > * Miniconda 4.7.10 is released on 2019-07-29 which is 4 years
> old
> > > > > already
> > > > > > > and not supporting too many architectures (x86_64 and ppc64le)
> > > > > > > * The latest miniconda which has real multi-arch feature set
> > > supports
> > > > > the
> > > > > > > following python versions: 3.8, 3.9, 3.10, 3.11 and no 3.7
> > support
> > > > > > >
> > > > > > > Suggestion to solve the issues:
> > > > > > > * In 1.19 drop python 3.7 support and upgrade miniconda to the
> > > latest
> > > > > > > version which opens the door to other platform + python 3.11
> > > support
> > > > > > >
> > > > > > > Please note python 3.11 support is not initiated/discussed
> here.
> > > > > > >
> > > > > > > BR,
> > > > > > > G
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > >
> > > --
> > > Best regards,
> > > Sergey
> > >
> >
>

Re: [VOTE] Apache Flink ML Release 2.3.0, release candidate #1

[Xingbo Huang]

+1 (binding)

- Verified the checksums and GPG files.
- Reviewed the website PR.
- Check the Python package apache-flink-ml-2.3.0.tar.gz

Best,
Xingbo

Dian Fu  于2023年6月29日周四 19:46写道：

> +1 (binding)
>
> - Verified the checksums and signatures.
> - The website PR LGTM
>
> Regards,
> Dian
>
> On Thu, Jun 29, 2023 at 7:03 PM Zhipeng Zhang 
> wrote:
> >
> > Thanks Dong and Xin for driving this release.
> >
> > +1 (non-binding)
> >
> > - Verified that the checksums and GPG files.
> > - Verified that the source distributions do not contain any binaries.
> > - Browsed through JIRA release notes files.
> > - Browsed through README.md files.
> >
> > Xin Jiang  于2023年6月29日周四 12:08写道：
> > >
> > > Hi Dong,
> > >
> > > Thanks for driving this release.
> > >
> > > +1 (non-binding)
> > >
> > > - Verified that the checksums and GPG files.
> > > - Verified that the source distributions do not contain any binaries.
> > > - Built the source distribution and run all unit tests.
> > > - Verified that all POM files point to the same version.
> > > - Browsed through JIRA release notes files.
> > > - Browsed through README.md files.
> > >
> > >
> > > Best Regards,
> > > Xin
> >
> >
> >
> > --
> > best,
> > Zhipeng
>

Re: [VOTE] Release 1.16.2, release candidate #1

[Xingbo Huang]

+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.7
- reviewed release blog post

Best,
Xingbo

Xintong Song  于2023年5月21日周日 13:03写道：

> +1 (binding)
>
> - verified signatures and checksums
> - built from source
> - tried example jobs with a standalone cluster, everything seems fine
> - review release announcement PR
>
> Best,
>
> Xintong
>
>
>
> On Sat, May 20, 2023 at 6:04 PM Jing Ge 
> wrote:
>
> > +1(non-binding)
> >
> > - reviewed Jira release notes
> > - built from source
> > - apache repos contain all necessary files
> > - verified signatures
> > - verified hashes
> > - verified tag
> > - reviewed PR
> >
> > Best regards,
> > Jing
> >
> > On Sat, May 20, 2023 at 11:51 AM Yun Tang  wrote:
> >
> > > +1 (non-binding)
> > >
> > >
> > >   *   Verified signatures
> > >   *   Reviewed the flink-web PR
> > >   *   Set up a standalone cluster from released binaries and check the
> > git
> > > revision number.
> > >   *   Submit the statemachine example with RocksDB, and it works fine.
> > >
> > > Best,
> > > Yun Tang
> > > 
> > > From: Yuxin Tan 
> > > Sent: Friday, May 19, 2023 17:41
> > > To: dev@flink.apache.org 
> > > Subject: Re: [VOTE] Release 1.16.2, release candidate #1
> > >
> > > +1 (non-binding)
> > >
> > > - Verified signature
> > > - Verified hashes
> > > - Build form source with mac
> > > - Verify that the source archives do not contain any binaries
> > > - Run streaming and batch job in sql-client successfully.
> > >
> > > Thanks weijie for driving this release candidate.
> > >
> > > Best,
> > > Yuxin
> > >
> > >
> > > weijie guo  于2023年5月19日周五 16:19写道：
> > >
> > > > Hi everyone,
> > > >
> > > >
> > > > Please review and vote on the release candidate #1 for the version
> > > 1.16.2,
> > > >
> > > > 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],
> > > >
> > > > * the official Apache source release and binary convenience releases
> to
> > > be
> > > >
> > > > deployed to dist.apache.org [2], which are signed with the key with
> > > >
> > > > fingerprint 8D56AE6E7082699A4870750EA4E8C4C05EE6861F [3],
> > > >
> > > > * all artifacts to be deployed to the Maven Central Repository [4],
> > > >
> > > > * source code tag "release-1.16.2-rc1" [5],
> > > >
> > > > * website pull request listing the new release and adding
> announcement
> > > blog
> > > >
> > > > post [6].
> > > >
> > > >
> > > > The vote will be open for at least 72 hours. It is adopted by
> majority
> > > >
> > > > approval, with at least 3 PMC affirmative votes.
> > > >
> > > >
> > > > Thanks,
> > > >
> > > > Release Manager
> > > >
> > > >
> > > > [1]
> > > >
> > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12352765
> > > >
> > > > [2] https://dist.apache.org/repos/dist/dev/flink/flink-1.16.2-rc1/
> > > >
> > > > [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> > > >
> > > > [4]
> > > >
> > https://repository.apache.org/content/repositories/orgapacheflink-1634/
> > > >
> > > > [5] https://github.com/apache/flink/releases/tag/release-1.16.2-rc1
> > > >
> > > > [6] https://github.com/apache/flink-web/pull/649
> > > >
> > >
> >
>

Re: [VOTE] Release 1.17.1, release candidate #1

[Xingbo Huang]

+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 blog post

Best,
Xingbo

Yuxin Tan  于2023年5月22日周一 18:55写道：

> +1 (non-binding)
>
> - verified the signatures
> - verified the checksums
> - built from source
> - start a standalone cluster, run a simple batch and a streaming job
> successfully
> - review release announcement PR
>
> Best,
> Yuxin
>
>
> Xintong Song  于2023年5月22日周一 18:24写道：
>
> > +1 (binding)
> >
> > - verified signatures and checksums
> > - built from source
> > - tried example jobs with a standalone cluster, everything seems fine
> > - review release announcement PR
> >
> > Best,
> >
> > Xintong
> >
> >
> >
> > On Mon, May 22, 2023 at 2:18 PM weijie guo 
> > wrote:
> >
> > > Hi everyone,
> > >
> > >
> > > Please review and vote on the release candidate #1 for the version
> > 1.17.1,
> > >
> > > 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],
> > >
> > > * the official Apache source release and binary convenience releases to
> > be
> > >
> > > deployed to dist.apache.org [2], which are signed with the key with
> > >
> > > fingerprint 8D56AE6E7082699A4870750EA4E8C4C05EE6861F [3],
> > >
> > > * all artifacts to be deployed to the Maven Central Repository [4],
> > >
> > > * source code tag "release-1.17.1-rc1" [5],
> > >
> > > * website pull request listing the new release and adding announcement
> > blog
> > >
> > > post [6].
> > >
> > >
> > > The vote will be open for at least 72 hours. It is adopted by majority
> > >
> > > approval, with at least 3 PMC affirmative votes.
> > >
> > >
> > > Thanks,
> > >
> > > Release Manager
> > >
> > >
> > > [1]
> > >
> > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12352886
> > >
> > > [2] https://dist.apache.org/repos/dist/dev/flink/flink-1.17.1-rc1/
> > >
> > > [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> > >
> > > [4]
> > >
> https://repository.apache.org/content/repositories/orgapacheflink-1635/
> > >
> > > [5] https://github.com/apache/flink/releases/tag/release-1.17.1-rc1
> > >
> > > [6] https://github.com/apache/flink-web/pull/650
> > >
> >
>

Re: [VOTE] Apache Flink ML Release 2.2.0, release candidate #2

[Xingbo Huang]

Thanks Dong for driving this release.

+1 (binding)

- verify signatures and checksums
- pip install apache-flink-ml source package and run simple example
- download source code and build from source code
- review release notes

Best,
Xingbo

Guowei Ma  于2023年4月14日周五 15:54写道：

> Hi Dong,
>
> Thanks for driving this release!
>
> +1 (binding)
>
> * Checked JIRA release notes
> * Verified signature and checksum for the source
> * Download the source code and build the code with JDK8
> * Browsed through README.md files.
>
> Best,
> Guowei
>
>
> On Fri, Apr 14, 2023 at 2:48 PM Zhipeng Zhang 
> wrote:
>
> > Hi Dong,
> > Thanks for driving this release!
> >
> > +1 (non-binding)
> >
> > Here is what I have checked.
> > - Verified that the checksums and GPG files.
> > - Verified that the source distributions do not contain any binaries.
> > - Built the source distribution and run all unit tests.
> > - Verified that all POM files point to the same version.
> > - Browsed through JIRA release notes files.
> > - Browsed through README.md files.
> > - Verified the source code tag.
> >
> >
> > Dong Lin  于2023年4月13日周四 18:28写道：
> >
> > >
> > > Hi everyone,
> > >
> > > Please review and vote on the release candidate #2 for version 2.2.0 of
> > > Apache Flink ML as follows:
> > >
> > > [ ] +1, Approve the release
> > > [ ] -1, Do not approve the release (please provide specific comments)
> > >
> > > **Testing Guideline**
> > >
> > > You can find here [1] a page in the project wiki on instructions for
> > > testing.
> > >
> > > To cast a vote, it is not necessary to perform all listed checks, but
> > > please mention which checks you have performed when voting.
> > >
> > > **Release Overview**
> > >
> > > As an overview, the release consists of the following:
> > > a) Flink ML source release to be deployed to dist.apache.org
> > > b) Flink ML Python source distributions to be deployed to PyPI
> > > c) Maven artifacts to be deployed to the Maven Central Repository
> > >
> > > **Staging Areas to Review**
> > >
> > > The staging areas containing the above-mentioned artifacts are as
> > follows, for
> > > your review:
> > >
> > > - All artifacts for a) and b) can be found in the corresponding dev
> > repository
> > > at dist.apache.org [2], which are signed with the key with fingerprint
> > AFAC
> > > DB09 E6F0 FF28 C93D 64BC BEED 4F6C B9F7 7D0E [3]
> > > - All artifacts for c) can be found at the Apache Nexus Repository [4]
> > >
> > > **Other links for your review**
> > >
> > > - JIRA release notes [5]
> > > - Source code tag "release-2.2.0-rc2" [6]
> > > - PR to update the website Downloads page to include Flink ML links [7]
> > >
> > > **Vote Duration**
> > >
> > > The voting time will run for at least 72 hours. It is adopted by
> majority
> > > approval, with at least 3 PMC affirmative votes.
> > >
> > >
> > > Cheers,
> > > Dong
> > >
> > >
> > > [1]
> > https://cwiki.apache.org/confluence/display/FLINK/Verifying+a+Flink+ML+
> > > Release
> > > [2] https://dist.apache.org/repos/dist/dev/flink/flink-ml-2.2.0-rc2/
> > > [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> > > [4]
> > https://repository.apache.org/content/repositories/orgapacheflink-1605/
> > > [5]
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12351884
> > > [6] https://github.com/apache/flink-ml/releases/tag/release-2.2.0-rc2
> > > [7] https://github.com/apache/flink-web/pull/630
> >
> >
> >
> > --
> > best,
> > Zhipeng
> >
>

Re: [VOTE] Release 1.17.0, release candidate #3

[Xingbo Huang]

+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 Nuyanzin  于2023年3月21日周二 18:41写道：

> +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 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 (not-binding)
> >
> > Best Etienne
> >
> > Le 17/03/2023 à 15:01, Qingsheng Ren a écrit :
> > > 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], and the pull request adding release note for
> > > users [2]
> > > * the official Apache source release and binary convenience releases to
> > be
> > > deployed to dist.apache.org [3], which are signed with the key with
> > > fingerprint A1BD477F79D036D2C30CA7DBCA8AEEC2F6EB040B [4],
> > > * all artifacts to be deployed to the Maven Central Repository [5],
> > > * source code tag "release-1.17.0-rc3" [6],
> > > * website pull request listing the new release and adding announcement
> > blog
> > > post [7].
> > >
> > > The vote will be open for at least 72 hours. It is adopted by majority
> > > approval, with at least 3 PMC affirmative votes.
> > >
> > > [1]
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12351585
> > > [2] https://github.com/apache/flink/pull/22146
> > > [3] https://dist.apache.org/repos/dist/dev/flink/flink-1.17.0-rc3/
> > > [4] https://dist.apache.org/repos/dist/release/flink/KEYS
> > > [5]
> > https://repository.apache.org/content/repositories/orgapacheflink-1600
> > > [6] https://github.com/apache/flink/releases/tag/release-1.17.0-rc3
> > > [7] https://github.com/apache/flink-web/pull/618
> > >
> > > Thanks,
> > > Martijn and Matthias, Leonard and Qingsheng
> > >
> >
>

Re: [VOTE] Release 1.15.4, release candidate #2

[Xingbo Huang]

+1 (binding)

- checked signatures and checksums of binaries
- reviewed release blog post
- verify python wheel package contents
- run the examples from Python Table API tutorial

Thanks for preparing this rc!

Xingbo

Samrat Deb  于2023年3月14日周二 10:16写道：

> +1 (non binding)
>
>   - checked AWS SDKv2 version has been bumped to 2.19.14 through
> FLINK-30633 and
> all NOTICE files updates
> - Checked release notes
> - Checked sum and signatures
> - Maven clean install from source
> - Checked the jars in the staging repo
> - Checked website updates
>
> Bests,
> Samrat
>
> On Tue, 14 Mar 2023 at 7:36 AM, Dian Fu  wrote:
>
> > +1 (binding)
> >
> > - Verified the checksum and signature
> > - Installed PyFlink on MacOS and run a word count example successfully
> > - The website PR LGTM
> >
> > Regards,
> > Dian
> >
> > On Thu, Mar 9, 2023 at 8:22 PM Danny Cranmer 
> > wrote:
> >
> > > Hi everyone,
> > > Please review and vote on the release candidate #2 for the version
> > 1.15.4,
> > > 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],
> > > * the official Apache source release and binary convenience releases to
> > be
> > > deployed to dist.apache.org [2], which are signed with the key with
> > > fingerprint 125FD8DB [3],
> > > * all artifacts to be deployed to the Maven Central Repository [4],
> > > * source code tag "release-1.15.4-rc2" [5],
> > > * website pull request listing the new release and adding announcement
> > blog
> > > post [6].
> > >
> > > The vote will be open for at least 72 hours (excluding weekends
> > 2023-03-14
> > > 13:00). It is adopted by majority approval, with at least 3 PMC
> > affirmative
> > > votes.
> > >
> > > Thanks,
> > > Danny
> > >
> > > [1]
> > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12352526
> > > [2] https://dist.apache.org/repos/dist/dev/flink/flink-1.15.4-rc2/
> > > [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> > > [4]
> > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheflink-1594/org/apache/flink/
> > > [5] https://github.com/apache/flink/releases/tag/release-1.15.4-rc2
> > > [6] https://github.com/apache/flink-web/pull/611
> > >
> >
>

Re: [DISCUSS] Extending the feature freezing date of Flink 1.17

[Xingbo Huang]

+1 for extending the freeze date to Jan 31st

Best,
Xingbo

Jingsong Li  于2023年1月3日周二 17:58写道：

> +1
>
> On Tue, Jan 3, 2023 at 4:40 PM Matthias Pohl
>  wrote:
> >
> > +1 for extending to Jan 31
> >
> > On Tue, Jan 3, 2023 at 8:33 AM Yu Li  wrote:
> >
> > > +1 for the proposal (extending the 1.17 feature freeze date to Jan
> 31st).
> > >
> > > Best Regards,
> > > Yu
> > >
> > >
> > > On Tue, 3 Jan 2023 at 15:11, Zhu Zhu  wrote:
> > >
> > > > +1 to extend the feature freeze date to Jan 31st.
> > > >
> > > > Thanks,
> > > > Zhu
> > > >
> > > > David Anderson  于2023年1月3日周二 11:41写道：
> > > > >
> > > > > I'm also in favor of extending the feature freeze to Jan 31st.
> > > > >
> > > > > David
> > > > >
> > > > > On Thu, Dec 29, 2022 at 9:01 AM Leonard Xu 
> wrote:
> > > > >
> > > > > > Thanks Qingsheng for the proposal, the pandemic has really
> impacted
> > > > > > development schedules.
> > > > > >
> > > > > > Jan 31st makes sense to me.
> > > > > >
> > > > > >
> > > > > > Best,
> > > > > > Leonard
> > > > > >
> > > > > >
> > > >
> > >
>

[jira] [Created] (FLINK-30366) Python Group Agg failed in cleaning the idle state

[Xingbo Huang (Jira)]

Xingbo Huang created FLINK-30366:


 Summary: Python Group Agg failed in cleaning the idle state
 Key: FLINK-30366
 URL: https://issues.apache.org/jira/browse/FLINK-30366
 Project: Flink
  Issue Type: Bug
  Components: API / Python
Affects Versions: 1.15.3, 1.16.0
Reporter: Xingbo Huang
Assignee: Xingbo Huang
 Fix For: 1.17.0, 1.16.1, 1.15.4


{code:java}
# aggregate_fast.pyx
cpdef void on_timer(self, InternalRow key):
if self.state_cleaning_enabled:
self.state_backend.set_current_key(key) # The key must be a list, but 
it is a InternalRow here.
accumulator_state = self.state_backend.get_value_state(
"accumulators", self.state_value_coder)
accumulator_state.clear()
self.aggs_handle.cleanup() {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (FLINK-30169) Adds version switcher in PyFlink API doc

[Xingbo Huang (Jira)]

Xingbo Huang created FLINK-30169:


 Summary: Adds version switcher in PyFlink API doc
 Key: FLINK-30169
 URL: https://issues.apache.org/jira/browse/FLINK-30169
 Project: Flink
  Issue Type: Sub-task
  Components: API / Python, Documentation
Reporter: Xingbo Huang
Assignee: Xingbo Huang


Adds version switcher in PyFlink API doc



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [ANNOUNCE] New Apache Flink Committer - Matyas Orhidi

[Xingbo Huang]

Congrats Matyas!

Best,
Xingbo

Yanfei Lei  于2022年11月22日周二 11:18写道：

> Congrats Matyas! 
>
> Zheng Yu Chen  于2022年11月22日周二 11:15写道：
>
> > Congratulations ~ 
> >
> > Márton Balassi  于2022年11月21日周一 22:18写道：
> >
> > > Hi everyone,
> > >
> > > On behalf of the PMC, I'm very happy to announce Matyas Orhidi as a new
> > > Flink
> > > committer.
> > >
> > > Matyas has over a decade of experience of the Big Data ecosystem and
> has
> > > been working with Flink full time for the past 3 years. In the open
> > source
> > > community he is one of the key driving members of the Kubernetes
> Operator
> > > subproject. He implemented multiple key features in the operator
> > including
> > > the metrics system and the ability to dynamically configure watched
> > > namespaces. He enjoys spreading the word about Flink and regularly does
> > so
> > > via authoring blogposts and giving talks or interviews representing the
> > > community.
> > >
> > > Please join me in congratulating Matyas for becoming a Flink committer!
> > >
> > > Best,
> > > Marton
> > >
> >
> >
> > --
> > Best
> >
> > ConradJam
> >
>
>
> --
> Best,
> Yanfei
>

Re: [DISCUSS] Flink release retro

[Xingbo Huang]

Thanks for starting the discussion, Matthias!

When I was the 1.16 release manager, I checked the dev mailing list to see
what the release managers of the previous two versions did throughout the
release cycle. In release 1.16, after each release sync meeting, we would
send a summary email, which can help capture how the release cycle has
progressed. So we may not really need a dedicated retrospective meeting.
But I think it's a good idea to have a wiki to summarize and review what
can be improved after we finish a release. For example, the release cycle
for 1.16 was also longer than expected. It took almost three months from
the feature freeze to our final official release, a month longer than
expected.

Best,
Xingbo

Jing Ge  于2022年11月3日周四 04:56写道：

> Hi all,
>
> I figure it is a good idea and +1 for the async retro. More developers will
> learn from what the release process looks like, which will give them
> context to engage in future releases. It would be great if the conversation
> could somehow follow the traditional retro pattern, e.g. tagged with
> "Liked, learned, Lacked, and Longed for".
>
> Best regards,
> Jing
>
> On Wed, Nov 2, 2022 at 11:21 AM Martijn Visser 
> wrote:
>
> > Hi Matthias,
> >
> > I think it's a good idea to capture how this release cycle has
> progressed.
> > I'm not sure that a classical "retrospective" is the best solution, since
> > it would require multiple people in different timezones to attend a
> virtual
> > meeting.
> >
> > So I would +1 an async retrospective, which could be the questions that
> you
> > would normally ask during a retrospective yet but now via a
> questionnaire.
> > It probably makes sense to have a proposal of the questions that can be
> > asked, discuss them and then sent them out.
> >
> > WDYT?
> >
> > Thanks,
> >
> > Martijn
> >
> > On Wed, Nov 2, 2022 at 9:42 AM Qingsheng Ren  wrote:
> >
> > > Thanks for starting the discussion Matthias!
> > >
> > > I think having a retro after a release cycle would be quite helpful to
> > > standardizing the procedure of the release, and also could avoid new
> > > release managers getting stuck on the same issue that happened before.
> I
> > > prefer the second option that RMs could open a discussion thread in ML
> at
> > > the end of the release to collect feedback about the last release cycle
> > and
> > > add them to the release wiki page, which would be quite handy for
> further
> > > RMs.
> > >
> > > Best,
> > > Qingsheng
> > > Ververica (Alibaba)
> > >
> > > On Mon, Oct 31, 2022 at 11:02 PM Matthias Pohl
> > >  wrote:
> > >
> > > > Hi everyone,
> > > > I want to bring up the idea of having a retrospective on the release
> > from
> > > > the release manager's perspective. The idea would be to collect
> > feedback
> > > on
> > > > what went well and what could be improved for a specific minor
> release.
> > > So
> > > > far, I didn't find anything on that topic. Does the community find
> this
> > > > useful? Or was this already done but not helpful?
> > > >
> > > > I see three options here:
> > > > 1. Having an actual meeting where issues can be discussed and/or
> > > > experiences can be shared between the release managers of the
> previous
> > > > release and the release managers of the next minor release. Of
> course,
> > > this
> > > > could be open to other contributors as well. A summary could be
> > provided
> > > in
> > > > the Flink wiki (the Flink release's wiki article).
> > > > 2. The release manager(s) provide a summary on the Flink release's
> wiki
> > > > article as part of the release process.
> > > > 3. Leave the process as is without any additional retrospective but
> > focus
> > > > on improving the documentation if issues arose during the release.
> > > >
> > > > That might help people who consider contributing to the community
> > through
> > > > supporting the release efforts. Additionally, it might help in
> > > > understanding what went wrong in past releases retroactively (e.g.
> the
> > > > longer release cycle for 1.15).
> > > >
> > > > I'm curious about opinion's on that topic.
> > > >
> > > > Best,
> > > > Matthias
> > > >
> > >
> >
>

[ANNOUNCE] Apache Flink 1.16.0 released

[Xingbo Huang]

The Apache Flink community is very happy to announce the release of Apache
Flink 1.16.0, which is the first release for the Apache Flink 1.16 series.

Apache Flink® is an open-source stream processing framework for
distributed, high-performing, always-available, and accurate data streaming
applications.

The release is available for download at:
https://flink.apache.org/downloads.html

Please check out the release blog post for an overview of the
improvements for this release:
https://flink.apache.org/news/2022/10/28/1.16-announcement.html

The full release notes are available in Jira:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12351275

We would like to thank all contributors of the Apache Flink community
who made this release possible!

Regards,
Chesnay, Martijn, Godfrey & Xingbo

[RESULT] [VOTE] Release 1.16.0, release candidate #2

[Xingbo Huang]

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)
- Matthias (non-binding)
- Gyula (binding)
- Hong (non-binding)
- Yuxia (non-binding)
- JunRui (non-binding)
- Yanfei (non-binding)
- Mason (non-binding)
- Yang (binding)

There are no disapproving votes.

Thank you for verifying the release candidate. I will now proceed to
finalize the release and announce it once everything is published.

Best,
Xingbo

Re: [VOTE] Release 1.16.0, release candidate #2

[Xingbo Huang]

Thank you all for helping to verify the release. Really appreciated!
I will conclude the vote in a separate thread.

Best,
Xingbo

Yang Wang  于2022年10月25日周二 18:44写道：

> +1(binding)
>
> * Built from source
> * Verified signature and checksum
> * Build docker image with flink binary
> * Submit/stop a streaming and batch job with Flink Kubernetes Operator and
> everything works well
> * Check the metrics and logs via ingress webUI
>
>
> Best,
> Yang
>
> Mason Chen  于2022年10月25日周二 14:43写道：
>
> > +1 (non-binding)
> >
> > * Built from source
> > * Verified signature and checksum
> > * Verified behavior/metrics/logs with internal stateful applications
> using
> > the Kafka source/sink connectors on K8s
> >
> > Best,
> > Mason
> >
> > On Mon, Oct 24, 2022 at 11:16 PM Leonard Xu  wrote:
> >
> > >
> > > > BTW, the "Add New" button in "Submit New Job" tab can't work in my
> > local
> > > > standalone cluster, is this as expected?
> > >
> > > I checked this case it works well in my local env(MacOS + Chrome)，it
> > > should be your env issue.
> > >
> > > Best,
> > > Leonard Xu
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > >> +1 (non-binding) for this candidate
> > > >>
> > > >>  *   Built from the source code.
> > > >>  *   Ran batch wordcount jobs with slow nodes of different source
> > types
> > > on
> > > >> the yarn cluster.
> > > >>  *   The new source speculative execution works as expected, the
> > result
> > > is
> > > >> expected, no suspicious log output.
> > > >>  *   Slow nodes are successfully added to the blocklist and
> > subsequently
> > > >> removed as expected.
> > > >>  *   Ran large parallelism batch jobs and performance does not
> > degrade.
> > > >>
> > > >> 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 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 (non-binding)
> > > >>>
> > > >>> * Hashes and Signatures look good
> > > >>> * All required files on dist.apache.org
> > > >>> * Tag is present in Github
> > > >>> * Verified source archive does not contain any binary files
> > > >>> * Source archive builds using maven
> > > >>> * Deployed standalone session cluster and ran TopSpeedWindowing
> > example
> > > >> in
> > > >>> streaming with checkpointing enabled. Looks ok
> > > >>>
> > > >>> Cheers,
> > > >>> Hong
> > > >>>
> > > >>> On 24/10/2022, 16:06, "Gyula Fóra"  wrote:
> > > >>>
> > > >>>CAUTION: This email originated from outside of the organization.
> > Do
> > > >>> not click links or open attachments unless you can confirm the
> sender
> > > and
> > > >>> know the content is safe.
> > > >>>
> > > >>>
> > > >>>
> > > >>>+1 (binding)
> > > >>>
> > > >>>* Verified checksums/GPG signatures
> > > >>>* Built from source
> > > >>>* Tested with Kubernetes operator, including simple jobs,
> > > >>> checkpointing etc.
> > > >>>* Metrics, logs look good.
> > > >>>
> > > >>>Gyula
> > > >>>
> > > >>>On Mon, Oct 24, 2022 at 4:54 PM Matthias Pohl
> > > >>> wrote:
> > > >>>
> > > >>>> +1 (non-binding)
> > > >>>>

Re: [VOTE] Release 1.16.0, release candidate #2

[Xingbo Huang]

 pain. I'm curious what others think if this
> is
> > > worthy
> > > > > > of cancelling the release candidate.
> > > > > >
> > > > > > Thanks, Martijn
> > > > > >
> > > > > > On Thu, Oct 20, 2022 at 4:54 PM Krzysztof Chmielewski <
> > > > > > krzysiek.chmielew...@gmail.com> wrote:
> > > > > >
> > > > > > > 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 problem was
> > described
> > > by
> > > > > me
> > > > > > in
> > > > > > > this thread [1]. We need all three to fix the problem.
> > > > > > >
> > > > > > > All three tickets were merged into 1.15 release branch and will
> > be
> > > > > > included
> > > > > > > in 1.15.3 probably, however 1.16 will be missing one fix
> (29627).
> > > > > > > In other words, there will be a regression between 1.16 and
> > 1.15.3.
> > > > > > >
> > > > > > > Additionally for now this issue is blocking Flink migration for
> > > Delta
> > > > > > > connector [2].
> > > > > > > We need to migrate because Flink 1.14 has another Sink problem
> > with
> > > > > data
> > > > > > > loss during Sink Recovery with Global Committer [3] and this
> one
> > > most
> > > > > > > likely will not be fixed since 1.14 support is ending.
> > > > > > >
> > > > > > > Forgive my if I'm wrong but what do you mean by " we won't
> block
> > > 1.16.0
> > > > > > on
> > > > > > > this." Fix is merged so couldn't we just cherry pick 1.16 merge
> > > commit
> > > > > to
> > > > > > > 1.16.0's RC2?
> > > > > > >
> > > > > > > [1]
> > > https://lists.apache.org/thread/otscy199g1l9t3llvo8s2slntyn2r1jc
> > > > > > > [2] https://github.com/delta-io/connectors/tree/master/flink
> > > > > > > [3] https://issues.apache.org/jira/browse/FLINK-29589
> > > > > > >
> > > > > > > Regards,
> > > > > > > Krzysztof Chmielewski
> > > > > > >
> > > > > > > czw., 20 paź 2022 o 16:13 Xingbo Huang 
> > > napisał(a):
> > > > > > >
> > > > > > > > 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.
> > > > > > > >
> > > > > > > > Best,
> > > > > > > > Xingbo
> > > > > > > >
> > > > > > > > Xintong Song  于2022年10月20日周四 18:23写道：
> > > > > > > >
> > > > > > > > > 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
> > > > > > > b

Re: [DISCUSS] Planning Flink 1.17

[Xingbo Huang]

Thanks Qingsheng, Leonard and Martijn for starting the discussion and
volunteering.
The timeline proposal sounds reasonable :+1:

Best,
Xingbo

Jark Wu  于2022年10月21日周五 00:17写道：

> Thanks for kicking off the 1.17 release.
>
> Targeting feature freeze on 1/17 for 1.17 release sounds pretty good to me.
> +1 for the volunteers as release managers.
>
> Best,
> Jark
> Ververica (Alibaba)
>
> On Thu, 20 Oct 2022 at 18:09, Matthias Pohl  .invalid>
> wrote:
>
> > Thanks for starting the discussion about Flink 1.17. I would be
> interested
> > in helping out around the release as well.
> >
> > Best,
> > Matthias
> >
> > On Thu, Oct 20, 2022 at 12:07 PM Xintong Song 
> > wrote:
> >
> > > Thanks for kicking this off.
> > >
> > > +1 for the proposed timeline.
> > >
> > > Also +1 for Qingsheng, Leonard and Martijn as the release managers.
> > Thanks
> > > for volunteering.
> > >
> > > Best,
> > >
> > > Xintong
> > >
> > >
> > >
> > > On Thu, Oct 20, 2022 at 3:59 PM Martijn Visser <
> martijnvis...@apache.org
> > >
> > > wrote:
> > >
> > > > Hi Qingsheng,
> > > >
> > > > I'm definitely interested in participating as a release manager
> again.
> > > >
> > > > Best regards,
> > > >
> > > > Martijn
> > > >
> > > > On Thu, Oct 20, 2022 at 9:47 AM Qingsheng Ren 
> > wrote:
> > > >
> > > > > Hi everyone,
> > > > >
> > > > > As we are approaching the official release of Flink 1.16, it’s a
> good
> > > > time
> > > > > to kick off some discussions and march toward 1.17.
> > > > >
> > > > > - Release managers
> > > > >
> > > > > Leonard Xu and I would like to volunteer as release managers for
> > 1.17,
> > > > and
> > > > > it would be great to have someone else working together on this
> > > release.
> > > > > Please let us know if you have any interest!
> > > > >
> > > > > - Timeline
> > > > >
> > > > > Having 1.16 will be released in the next few days and the 4 months
> > > > release
> > > > > cycle after that, we propose to set the feature freezing date on
> > > *January
> > > > > 17th, 2023* (aligned with our version number 1.17 :-)), so that
> > > everyone
> > > > > could enjoy the holiday season and Chinese new year.
> > > > >
> > > > > - What we’ll be focusing
> > > > >
> > > > > Similar to our previous releases, we’d like to keep an eye on the
> > > > > timeline, CI stability, release testing, and any communication and
> > > > > coordination across teams and developers. One thing we’d like to
> > > mention
> > > > in
> > > > > particular is compatibility, which is a frequent complaint from our
> > > > > ecosystem developers and users. We encourage all committers to do
> an
> > > > extra
> > > > > manual check to see if any public interface is touched before
> > merging a
> > > > PR.
> > > > > We could discuss details in another thread later and update the
> > > > > contributing guidelines to list which should be treated as public
> > APIs.
> > > > > Please feel free to raise any discussions if you have anything else
> > to
> > > > > emphasize specifically.
> > > > >
> > > > > - Collecting features
> > > > >
> > > > > We'll create a wiki page under this directory[1] for collecting new
> > > > > features targeted in 1.17 as we always did before to give everyone
> an
> > > > > overview and track the progress. Please don’t hesitate to share
> your
> > > > ideas
> > > > > on the page. In the meantime, we’d like to kindly invite our
> > committers
> > > > to
> > > > > think about and plan what we could deliver to developers and users
> in
> > > > this
> > > > > release.
> > > > >
> > > > > Looking forward to working with you all in the coming 1.17 release!
> > > > >
> > > > > Best regards,
> > > > > Qingsheng Ren and Leonard Xu
> > > > > Ververica (Alibaba)
> > > > >
> > > > > [1]
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/FLINK/Release+Management+and+Feature+Plan
> > > > >
> > > >
> > >
> >
>

Re: [VOTE] Release 1.16.0, release candidate #2

[Xingbo Huang]

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.

Best,
Xingbo

Xintong Song  于2022年10月20日周四 18:23写道：

> 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 this. If there's no other blockers discovered in the rc2, the fix
> of FLINK-29627 will be shipped in 1.16.1.
>
> Best,
>
> Xintong
>
>
> [1] https://github.com/apache/flink/commits/release-1.16.0-rc2
>
> On Thu, Oct 20, 2022 at 6:16 PM Krzysztof Chmielewski <
> krzysiek.chmielew...@gmail.com> wrote:
>
> > 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] https://issues.apache.org/jira/browse/FLINK-29512
> > [3] https://issues.apache.org/jira/browse/FLINK-29627
> >
> > Regards,
> > Krzysztof Chmielewski
> >
> > czw., 20 paź 2022 o 11:51 Martijn Visser 
> > napisał(a):
> >
> > > 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, 2022 at 11:47 AM Krzysztof Chmielewski <
> > > krzysiek.chmielew...@gmail.com> wrote:
> > >
> > > > 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] https://issues.apache.org/jira/browse/FLINK-29627
> > > > [2] https://github.com/apache/flink/pull/21115
> > > > [3] https://issues.apache.org/jira/browse/FLINK-29509
> > > > [4] https://issues.apache.org/jira/browse/FLINK-29512
> > > >
> > > > Regards,
> > > > Krzysztof Chmielewski
> > > >
> > > > czw., 20 paź 2022 o 11:21 Xingbo Huang  napisał(a):
> > > >
> > > > > 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],
> > > > > * the official Apache source release and binary convenience
> releases
> > to
> > > > be
> > > > > deployed to dist.apache.org [2], which are signed with the key
> with
> > > > > fingerprint 3C2C9FFB59DF9F3E [3],
> > > > > * all artifacts to be deployed to the Maven Central Repository [4],
> > > > > * source code tag "release-1.16.0-rc2" [5],
> > > > > * website pull request listing the new release and adding
> > announcement
> > > > blog
> > > > > post [6].
> > > > >
> > > > > The vote will be open for at least 72 hours. It is adopted by
> > majority
> > > > > approval, with at least 3 PMC affirmative votes.
> > > > >
> > > > > Thanks,
> > > > > Chesnay, Martijn, Godfrey & Xingbo
> > > > >
> > > > > [1]
> > > > >
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12351275
> > > > > [2] https://dist.apache.org/repos/dist/dev/flink/flink-1.16.0-rc2
> > > > > [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> > > > > [4]
> > > >
> https://repository.apache.org/content/repositories/orgapacheflink-1541
> > > > > [5] https://github.com/apache/flink/tree/release-1.16.0-rc2
> > > > > [6] https://github.com/apache/flink-web/pull/574
> > > > >
> > > >
> > >
> >
>

[VOTE] Release 1.16.0, release candidate #2

[Xingbo Huang]

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],
* the official Apache source release and binary convenience releases to be
deployed to dist.apache.org [2], which are signed with the key with
fingerprint 3C2C9FFB59DF9F3E [3],
* all artifacts to be deployed to the Maven Central Repository [4],
* source code tag "release-1.16.0-rc2" [5],
* website pull request listing the new release and adding announcement blog
post [6].

The vote will be open for at least 72 hours. It is adopted by majority
approval, with at least 3 PMC affirmative votes.

Thanks,
Chesnay, Martijn, Godfrey & Xingbo

[1]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12351275
[2] https://dist.apache.org/repos/dist/dev/flink/flink-1.16.0-rc2
[3] https://dist.apache.org/repos/dist/release/flink/KEYS
[4] https://repository.apache.org/content/repositories/orgapacheflink-1541
[5] https://github.com/apache/flink/tree/release-1.16.0-rc2
[6] https://github.com/apache/flink-web/pull/574

Re: [VOTE] Reverting sink metric name changes made in 1.15

[Xingbo Huang]

+1

Best,
Xingbo

Xintong Song  于2022年10月14日周五 11:42写道：

> +1 (binding)
>
> Best,
>
> Xintong
>
>
>
> On Fri, Oct 14, 2022 at 11:19 AM Jark Wu  wrote:
>
> > Thanks a lot for driving this, Qingsheng!
> >
> > +1 (binding)
> >
> >
> > Best,
> > Jark
> >
> > On Fri, 14 Oct 2022 at 10:16, Hang Ruan  wrote:
> >
> > > +1 from me (non-binding).
> > >
> > > The documents about these Kafka sink metrics( Flink metrics
> > > <
> > >
> >
> https://nightlies.apache.org/flink/flink-docs-release-1.15/docs/ops/metrics//#scope
> > > >
> > > and Kafka sink monitoring
> > > <
> > >
> >
> https://nightlies.apache.org/flink/flink-docs-release-1.15/docs/connectors/datastream/kafka//#monitoring-1
> > > >)
> > > do not contain the usage of the metrics like numRecordsSend by now.
> Only
> > > Kinesis Sink contains these metrics.
> > > If the document about the metrics could be found in other places,
> please
> > > correct me. ;)
> > >
> > > Best,
> > > Hang
> > >
> > > Chesnay Schepler  于2022年10月14日周五 01:56写道：
> > >
> > > > Do we have a PoC that achieves this without re-introducing the bug
> > where
> > > > the numRecordsOut was simply wrong because it counted both records
> > > > written to the external system and the downstream committer?
> > > > It's gonna be quite the dirty hack I assume.
> > > >
> > > > On 13/10/2022 19:24, Qingsheng Ren wrote:
> > > > > Hi devs,
> > > > >
> > > > > I'd like to start a vote about reverting sink metric name changes
> > made
> > > in
> > > > > 1.15 considering compatibility issues. These metrics include:
> > > > >
> > > > > - numRecordsSend -> numRecordsOut
> > > > > - numRecordsSendPerSecond -> numRecordsOutPerSecond
> > > > > - numBytesSend -> numBytesOut
> > > > > - numBytesSendPerSecond -> numBytesOutPerSecond
> > > > > - numRecordsSendError -> numRecordsOutError
> > > > >
> > > > > which reflect the output of the sink to the external system. "send"
> > > > metric
> > > > > series will be kept with the same value as "out" metric series.
> This
> > > > change
> > > > > will be applied to 1.15 and 1.16. More details could be found in
> the
> > > > > discussion thread [1].
> > > > >
> > > > > The vote will open for at least 72 hours.
> > > > >
> > > > > Looking forward to your feedback!
> > > > >
> > > > > [1]
> https://lists.apache.org/thread/vxhty3q97s7pw2zn0jhkyd6sxwwodzbv
> > > > >
> > > > > Best,
> > > > > Qingsheng
> > > > >
> > > >
> > > >
> > >
> >
>

Re: [ANNOUNCE] New Apache Flink PMC Member - Danny Cranmer

[Xingbo Huang]

Congratulations Danny!

Best,
Xingbo

Sergey Nuyanzin  于2022年10月12日周三 01:26写道：

> Congratulations, Danny
>
> On Tue, Oct 11, 2022, 15:18 Lincoln Lee  wrote:
>
> > Congratulations Danny!
> >
> > Best,
> > Lincoln Lee
> >
> >
> > Congxian Qiu  于2022年10月11日周二 19:42写道：
> >
> > > Congratulations Danny!
> > >
> > > Best,
> > > Congxian
> > >
> > >
> > > Leonard Xu  于2022年10月11日周二 18:03写道：
> > >
> > > > Congratulations Danny!
> > > >
> > > >
> > > > Best,
> > > > Leonard
> > > >
> > > >
> > >
> >
>

[SUMMARY] Flink 1.16 release sync of 2022-10-11

[Xingbo Huang]

I would like to give you a brief update of the Flink 1.16 release sync
meating of 2022-10-11.

*rc1 is canceled because we found a metric compatibility change, which is
expected to be fixed before Thursday
https://issues.apache.org/jira/browse/FLINK-29567. We will prepare rc2 once
this blocker issue is fixed.*

*We still have some critical test stabilities[1] need to be resolved*

For more information about Flink release 1.16, you can refer to
https://cwiki.apache.org/confluence/display/FLINK/1.16+Release

The next Flink release sync will be on Tuesday the 18th of October at 9am
CEST/ 3pm China Standard Time / 7am UTC. The link could be found on the
following page
https://cwiki.apache.org/confluence/display/FLINK/1.16+Release#id-1.16Release-Syncmeeting
.

On behalf of all the release managers,

best regards,
Xingbo

[1] https://issues.apache.org/jira/issues/?filter=12352149

Re: [VOTE] Release 1.16.0, release candidate #1

[Xingbo Huang]

Hi everyone,

We have found a blocker issue
https://issues.apache.org/jira/browse/FLINK-29567, so the rc1 is officially
canceled. And I will prepare the next RC after the blocker issue is
resolved.

Best,
Xingbo

Congxian Qiu  于2022年10月10日周一 10:00写道：

> +1 (non-binding)
>
> - checked sha512 & gpg
> - tag in the GitHub repo seems ok
> - no binary files found in the source
> - check all versions in the pom file nothing suspicious found
> - compile from source ok
> - add one comment about the release blog
> - deploy standalone session cluster & application job, run streaming
> example jobs, seems ok
>
> Best,
> Congxian
>
>
> Teoh, Hong  于2022年10月9日周日 04:32写道：
>
> >
> > +1 (non-binding)
> >
> > * Hashes and Signatures look good
> > * All required files on dist.apache.org
> > * Tag is present in Github
> > * Verified source archive does not contain any binary files
> > * Source archive builds using maven
> > * Deployed standalone session cluster and ran TopSpeedWindowing example
> in
> > streaming. Looks ok
> > * Added a couple of nits to the release PR
> >
> > Cheers,
> > Hong
> >
> > On 04/10/2022, 12:56, "Matthias Pohl" 
> > wrote:
> >
> > CAUTION: This email originated from outside of the organization. Do
> > not click links or open attachments unless you can confirm the sender and
> > know the content is safe.
> >
> >
> >
> > +1 (non-binding)
> >
> > * Downloaded artifacts
> > * Verified checksums/GPG signatures
> > * Compared checkout with provided sources
> > * Verified pom file versions
> > * Went over NOTICE file/pom files changes without finding anything
> > suspicious
> > * Build Flink from sources
> > * Deployed standalone session cluster and ran WordCount example in
> > batch
> > and streaming: Nothing suspicious in log files found
> >
> > On Fri, Sep 30, 2022 at 3:56 PM Matthias Pohl <
> matthias.p...@aiven.io>
> > wrote:
> >
> > > Ok, I was wrong. The step is actually documented at the end of the
> > Flink
> > > release documentation [1] in item 15) in the "Checklist to declare
> > the
> > > process completed" subsection. I missed that one. Sorry for the
> > confusion.
> > >
> > > I revoke my veto and close FLINK-29485 [2].
> > >
> > > [1]
> > >
> >
> https://cwiki.apache.org/confluence/display/FLINK/Creating+a+Flink+Release
> > > [2] https://issues.apache.org/jira/browse/FLINK-29485
> > >
> > > On Fri, Sep 30, 2022 at 3:50 PM Matthias Pohl <
> > matthias.p...@aiven.io>
> > > wrote:
> > >
> > >> Probably, my expectations were wrong here: I expected that we want
> > to
> > >> test the compatibility in these tests between different major
> > versions and
> > >> that we would want to verify the current version of the release
> > branch as
> > >> well before releasing the artifacts. What's the rationale behind
> > doing it
> > >> after the artifacts are released?
> > >>
> > >> On Fri, Sep 30, 2022 at 3:37 PM Chesnay Schepler <
> > ches...@apache.org>
> > >> wrote:
> > >>
> > >>> Could you be more specific as to what you believe should be
> > updated?
> > >>>
> > >>> IIRC the release-1.16 branch only gets updated ta all once the
> > release
> > >>> is out (e.g., mark docs as stable, update japicmp reference).
> > >>>
> > >>> On 30/09/2022 15:32, Matthias Pohl wrote:
> > >>> > Looking into the git history, there are numerous locations that
> > need
> > >>> to be
> > >>> > updated in the release-1.16 branch. Yun Gao did a few commits
> > around
> > >>> that
> > >>> > topic (da9e6be..6f69f4e). But these changes were committed
> close
> > to the
> > >>> > actual release date rather than the release branch creation
> > date. Is
> > >>> this
> > >>> > part of the release steps [1]. It feels like it should be part
> > of the
> > >>> > section where we create the release branch. But cannot find the
> > >>> pointer.
> > >>> >
> > >>>

Re: [DISCUSS] Reverting sink metric name changes made in 1.15

[Xingbo Huang]

+1 for reverting these changes in Flink 1.16, so I will cancel 1.16.0-rc1.
+1 for `numXXXSend` as the alias of `numXXXOut` in 1.15.3.

Best,
Xingbo

Chesnay Schepler  于2022年10月10日周一 19:13写道：

> > I’m with Xintong’s idea to treat numXXXSend as an alias of numXXXOut
>
> But that's not possible. If it were that simple there would have never
> been a need to introduce another metric in the first place.
>
> It's a rather fundamental issue with how the new sinks work, in that they
> emit data to the external system (usually considered as "numRecordsOut" of
> sinks) while _also_ sending data to a downstream operator (usually
> considered as "numRecordsOut" of tasks).
> The original issue was that the numRecordsOut of the sink counted both
> (which is completely wrong).
>
> A new metric was always required; otherwise you inevitably end up breaking
> *some* semantic.
> Adding a new metric for what the sink writes to the external system is,
> for better or worse, more consistent with how these metrics usually work in
> Flink.
>
> On 10/10/2022 12:45, Qingsheng Ren wrote:
>
> Thanks everyone for joining the discussion!
>
> > Do you have any idea what has happened in the process here?
>
> The discussion in this PR [1] shows some details and could be helpful to
> understand the original motivation of the renaming. We do have a test case
> for guarding metrics but unfortunaly the case was also modified so the
> defense was broken.
>
> I think the reason why both the developer and the reviewer forgot to
> trigger an discussion and gave a green pass on the change is that metrics
> are quite “trivial” to be noticed as public APIs. As mentioned by Martijn I
> couldn’t find a place noting that metrics are public APIs and should be
> treated carefully while contributing and reviewing.
>
> IMHO three actions could be made to prevent this kind of changes in the
> future:
>
> a. Add test case for metrics (which we already have in SinkMetricsITCase)
> b. We emphasize that any public-interface breaking changes should be
> proposed by a FLIP or discussed in mailing list, and should be listed in
> the release note.
> c. We remind contributors and reviewers about what should be considered as
> public API, and include metric names in it.
>
> For b and c these two pages [2][3] might be proper places.
>
> About the patch to revert this, it looks like we have a consensus on 1.16.
> As of 1.15 I think it’s worthy to trigger a minor version. I didn’t see
> complaints about this for now so it should be OK to save the situation
> asap. I’m with Xintong’s idea to treat numXXXSend as an alias of numXXXOut
> considering there could possibly some users have already adapted their
> system to the new naming, and have another internal metric for reflecting
> number of outgoing committable batches (actually the numRecordsIn of sink
> committer operator should be carrying this info already).
>
> [1] https://github.com/apache/flink/pull/18825
> [2] https://flink.apache.org/contributing/contribute-code.html
> [3] https://flink.apache.org/contributing/reviewing-prs.html
>
> Best,
> Qingsheng
> On Oct 10, 2022, 17:40 +0800, Xintong Song 
> , wrote:
>
> +1 for reverting these changes in Flink 1.16.
>
> For 1.15.3, can we make these metrics available via both names (numXXXOut
> and numXXXSend)? In this way we don't break it for those who already
> migrated to 1.15 and numXXXSend. That means we still need to change
> SinkWriterOperator to use another metric name in 1.15.3, which IIUC is
> internal to Flink sink.
>
> I'm overall +1 to change numXXXOut back to its original semantics. AFAIK
> (from meetup / flink-forward questionaires), most users do not migrate to a
> new Flink release immediately, until the next 1-2 major releases are out.
>
> Best,
>
> Xintong
>
>
> On Mon, Oct 10, 2022 at 5:26 PM Martijn Visser 
> wrote:
>
>> Hi Qingsheng,
>>
>> Do you have any idea what has happened in the process here? Do we know why
>> they were changed? I was under the impression that these metric names were
>> newly introduced due to the new interfaces and because it still depends on
>> each connector implementing these.
>>
>> Sidenote: metric names are not mentioned in the FLIP process as a public
>> API. Might make sense to have a separate follow-up to add that to the list
>> (I do think we should list them there).
>>
>> +1 for reverting this and make this change in Flink 1.16
>>
>> I'm not in favour of releasing a Flink 1.15.3 with this change: I think
>> the
>> impact is too big for a patch version, especially given how long Flink
>> 1.15
>> is already out there.
>>
>> Best regards,
>>
>> Martijn
>>
>> On Mon, Oct 10, 2022 at 11:13 AM Leonard Xu  wrote:
>>
>> > Thanks Qingsheng for starting this thread.
>> >
>> > +1 on reverting sink metric name and releasing 1.15.3 to fix this
>> > inconsistent behavior.
>> >
>> >
>> > Best,
>> > Leonard
>> >
>> >
>> >
>> >
>> >
>> > 2022年10月10日 下午3:06，Jark Wu  写道：
>> >
>> > Thanks for discovering this problem, Qingsheng!
>> >

[SUMMARY] Flink 1.16 release sync of 2022-10-04

[Xingbo Huang]

I would like to give you a brief update of the Flink 1.16 release sync
meating of 2022-10-04.

*We have prepared rc1 last Friday. Looking forward to your testing.*

*This week is Chinese National Day holiday, so the release time maybe a
week later than expected*

*We still have some critical test stabilities[1] need to be resolved*

For more information about Flink release 1.16, you can refer to
https://cwiki.apache.org/confluence/display/FLINK/1.16+Release

The next Flink release sync will be on Tuesday the 11th of October at 9am
CEST/ 3pm China Standard Time / 7am UTC. The link could be found on the
following page
https://cwiki.apache.org/confluence/display/FLINK/1.16+Release#id-1.16Release-Syncmeeting
.

On behalf of all the release managers,

best regards,
Xingbo

[1] https://issues.apache.org/jira/issues/?filter=12352149

[jira] [Created] (FLINK-29495) PulsarSinkE2ECase hang

[Xingbo Huang (Jira)]

Xingbo Huang created FLINK-29495:


 Summary: PulsarSinkE2ECase hang
 Key: FLINK-29495
 URL: https://issues.apache.org/jira/browse/FLINK-29495
 Project: Flink
  Issue Type: Bug
  Components: Connectors / Pulsar
Affects Versions: 1.15.2, 1.16.0, 1.17.0
Reporter: Xingbo Huang


{code:java}
2022-10-02T05:53:56.0611489Z "main" #1 prio=5 os_prio=0 cpu=5171.60ms 
elapsed=9072.82s tid=0x7f9508028000 nid=0x54ef1 waiting on condition  
[0x7f950f994000]
2022-10-02T05:53:56.0612041Zjava.lang.Thread.State: TIMED_WAITING (parking)
2022-10-02T05:53:56.0612475Zat 
jdk.internal.misc.Unsafe.park(java.base@11.0.16.1/Native Method)
2022-10-02T05:53:56.0613302Z- parking to wait for  <0x87d261f8> (a 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
2022-10-02T05:53:56.0613959Zat 
java.util.concurrent.locks.LockSupport.parkNanos(java.base@11.0.16.1/LockSupport.java:234)
2022-10-02T05:53:56.0614661Zat 
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(java.base@11.0.16.1/AbstractQueuedSynchronizer.java:2123)
2022-10-02T05:53:56.0615428Zat 
org.apache.pulsar.common.util.collections.GrowableArrayBlockingQueue.poll(GrowableArrayBlockingQueue.java:203)
2022-10-02T05:53:56.0616165Zat 
org.apache.pulsar.client.impl.MultiTopicsConsumerImpl.internalReceive(MultiTopicsConsumerImpl.java:370)
2022-10-02T05:53:56.0616807Zat 
org.apache.pulsar.client.impl.ConsumerBase.receive(ConsumerBase.java:198)
2022-10-02T05:53:56.0617486Zat 
org.apache.flink.connector.pulsar.testutils.sink.PulsarPartitionDataReader.poll(PulsarPartitionDataReader.java:72)
 {code}
https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=41526=logs=6e8542d7-de38-5a33-4aca-458d6c87066d=5846934b-7a4f-545b-e5b0-eb4d8bda32e1



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[VOTE] Release 1.16.0, release candidate #1

[Xingbo Huang]

Hi everyone,

Please review and vote on the release candidate #1 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],
* the official Apache source release and binary convenience releases to be
deployed to dist.apache.org [2], which are signed with the key with
fingerprint 3C2C9FFB59DF9F3E [3],
* all artifacts to be deployed to the Maven Central Repository [4],
* source code tag "release-1.16.0-rc1" [5],
* website pull request listing the new release and adding announcement blog
post [6].

The vote will be open for at least 72 hours. It is adopted by majority
approval, with at least 3 PMC affirmative votes.

Thanks,
Chesnay, Martijn, Godfrey & Xingbo

[1]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12351275
[2] https://dist.apache.org/repos/dist/dev/flink/flink-1.16.0-rc1
[3] https://dist.apache.org/repos/dist/release/flink/KEYS
[4] https://repository.apache.org/content/repositories/orgapacheflink-1537
[5] https://github.com/apache/flink/tree/release-1.16.0-rc1
[6] https://github.com/apache/flink-web/pull/574

[ANNOUNCE] Apache Flink 1.14.6 released

[Xingbo Huang]

The Apache Flink community is very happy to announce the release of Apache
Flink 1.14.6, which is the fifth bugfix release for the Apache Flink 1.14
series.

Apache Flink® is an open-source stream processing framework for
distributed, high-performing, always-available, and accurate data streaming
applications.

The release is available for download at:
https://flink.apache.org/downloads.html

Please check out the release blog post for an overview of the improvements
for this bugfix release:
https://flink.apache.org/news/2022/09/28/release-1.14.6.html

The full release notes are available in Jira:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12351834

We would like to thank all contributors of the Apache Flink community who
made this release possible!

Regards,
Xingbo

[SUMMARY] Flink 1.16 release sync of 2022-09-27

[Xingbo Huang]

I would like to give you a brief update of the Flink 1.16 release sync
meating of 2022-09-27.

*Currently, there are still 2 blocker issues FLINK-29348, FLINK-29431. Once
these two issues are resolved and there are no other new blocking issues,
we will start preparing rc1.*

*We still have some critical test stabilities[1] need to be resolved*

*Welcome to put forward your valuable comments on release notes[2] and
release announcement[3]*

For more information about Flink release 1.16, you can refer to
https://cwiki.apache.org/confluence/display/FLINK/1.16+Release

The next Flink release sync will be on Tuesday the 4th of October at 9am
CEST/ 3pm China Standard Time / 7am UTC. The link could be found on the
following page
https://cwiki.apache.org/confluence/display/FLINK/1.16+Release#id-1.16Release-Syncmeeting
.

On behalf of all the release managers,

best regards,
Xingbo

[1] https://issues.apache.org/jira/issues/?filter=12352149
[2] https://github.com/apache/flink/pull/20859
[3]
https://docs.google.com/document/d/1rIBNpzJulqEKJCuYtWtG-vDmSsGpN9sip_ewpzMequ0/edit#

[RESULT] [VOTE] Release 1.14.6, release candidate #2

[Xingbo Huang]

Hi everyone,

I am pleased to announce that we have unanimously approved this release
candidate:

There are 7 approving votes, 3 of which are binding:
- Danny Cranmer (non-binding)
- Matthias Pohl (non-binding)
- Jingsong Li (binding)
- Yun Tang (non-binding)
- Dian Fu (binding)
- Yun Gao (binding)
- Jing Ge (non-binding)

There are no disapproving votes.

Thank you for verifying the release candidate. I will now proceed to
finalize the release and announce it once everything is published.

Best,
Xingbo

[SUMMARY] Flink 1.16 release sync of 2022-09-20

[Xingbo Huang]

I would like to give you a brief update of the Flink 1.16 release sync
meating of 2022-09-20.

*We have created release-1.16 rc0 in last Wednesday(14th of September 2022)*

*Currently, there are 3 blocker issues which are being worked on. Many
thanks to these contributors and reviewers.
- FLINK-29219, FLINK-29274, FLINK-29315

*We still have some critical test stabilities[1] need to be resolved*

*We are preparing release notes[2] and release announcement[3]*

For more information about Flink release 1.16, you can refer to
https://cwiki.apache.org/confluence/display/FLINK/1.16+Release

The next Flink release sync will be on Tuesday the 27th of September at 9am
CEST/ 3pm China Standard Time / 7am UTC. The link could be found on the
following page
https://cwiki.apache.org/confluence/display/FLINK/1.16+Release#id-1.16Release-Syncmeeting
.

On behalf of all the release managers,

best regards,
Xingbo

[1]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLINK%20AND%20issuetype%20%3D%20Bug%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20priority%20in%20(Blocker%2C%20Critical)%20AND%20fixVersion%20%3D%201.16.0%20ORDER%20BY%20summary%20ASC%2C%20priority%20DESC
[2] https://github.com/apache/flink/pull/20859
[3]
https://docs.google.com/document/d/1rIBNpzJulqEKJCuYtWtG-vDmSsGpN9sip_ewpzMequ0/edit#

[ANNOUNCE] Release 1.16.0, release candidate #0

[Xingbo Huang]

Hi everyone,

The RC0 for Apache Flink 1.16.0 has been created. This is still a
preview-only release candidate to facilitate the integrated testing since
there are still some ongoing efforts, thus no official votes will take
place. It has all the artifacts that we would typically have for a release,
except for the release note and the website pull request for the release
announcement.

The following contents are available for your review:
- the preview source release and binary convenience releases [1], which are
signed with the key with fingerprint 3C2C9FFB59DF9F3E [2].
- all artifacts that would normally be deployed to the Maven Central
Repository [3].
- source code tag "release-1.16.0-rc0" [4]

Your help testing the release will be greatly appreciated! And we'll create
the votable RC1 as soon as all the efforts are finished.

Thank you~
Chesnay, Martijn, Godfrey & Xingbo

[1] https://dist.apache.org/repos/dist/dev/flink/flink-1.16.0-rc0/
[2] https://dist.apache.org/repos/dist/release/flink/KEYS
[3] https://repository.apache.org/content/repositories/orgapacheflink-1532/
[4] https://github.com/apache/flink/releases/tag/release-1.16.0-rc0

[jira] [Created] (FLINK-29296) OperatorCoordinatorHolder.create throws NPE

[Xingbo Huang (Jira)]

Xingbo Huang created FLINK-29296:


 Summary: OperatorCoordinatorHolder.create throws NPE
 Key: FLINK-29296
 URL: https://issues.apache.org/jira/browse/FLINK-29296
 Project: Flink
  Issue Type: Bug
  Components: Runtime / Coordination
Affects Versions: 1.16.0
Reporter: Xingbo Huang
 Fix For: 1.16.0


{code:java}
2022-09-13T15:22:42.3864318Z Sep 13 15:22:42 [ERROR] Tests run: 8, Failures: 0, 
Errors: 1, Skipped: 0, Time elapsed: 5.633 s <<< FAILURE! - in 
org.apache.flink.test.streaming.runtime.SourceNAryInputChainingITCase
2022-09-13T15:22:42.3865377Z Sep 13 15:22:42 [ERROR] 
org.apache.flink.test.streaming.runtime.SourceNAryInputChainingITCase.testDirectSourcesOnlyExecution
  Time elapsed: 0.165 s  <<< ERROR!
2022-09-13T15:22:42.3867571Z Sep 13 15:22:42 java.lang.RuntimeException: Failed 
to fetch next result
2022-09-13T15:22:42.3919112Z Sep 13 15:22:42at 
org.apache.flink.streaming.api.operators.collect.CollectResultIterator.nextResultFromFetcher(CollectResultIterator.java:109)
2022-09-13T15:22:42.3920935Z Sep 13 15:22:42at 
org.apache.flink.streaming.api.operators.collect.CollectResultIterator.hasNext(CollectResultIterator.java:80)
2022-09-13T15:22:42.3922442Z Sep 13 15:22:42at 
org.apache.flink.streaming.api.datastream.DataStreamUtils.collectBoundedStream(DataStreamUtils.java:106)
2022-09-13T15:22:42.3924085Z Sep 13 15:22:42at 
org.apache.flink.test.streaming.runtime.SourceNAryInputChainingITCase.testDirectSourcesOnlyExecution(SourceNAryInputChainingITCase.java:89)
2022-09-13T15:22:42.3925493Z Sep 13 15:22:42at 
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
2022-09-13T15:22:42.3926635Z Sep 13 15:22:42at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
2022-09-13T15:22:42.3928378Z Sep 13 15:22:42at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
2022-09-13T15:22:42.3964273Z Sep 13 15:22:42at 
java.lang.reflect.Method.invoke(Method.java:498)
2022-09-13T15:22:42.3965054Z Sep 13 15:22:42at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
2022-09-13T15:22:42.3965788Z Sep 13 15:22:42at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
2022-09-13T15:22:42.3966508Z Sep 13 15:22:42at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
2022-09-13T15:22:42.3967476Z Sep 13 15:22:42at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
2022-09-13T15:22:42.3968432Z Sep 13 15:22:42at 
org.apache.flink.util.TestNameProvider$1.evaluate(TestNameProvider.java:45)
2022-09-13T15:22:42.3969233Z Sep 13 15:22:42at 
org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:61)
2022-09-13T15:22:42.3969871Z Sep 13 15:22:42at 
org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
2022-09-13T15:22:42.3970534Z Sep 13 15:22:42at 
org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
2022-09-13T15:22:42.3971453Z Sep 13 15:22:42at 
org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
2022-09-13T15:22:42.3972453Z Sep 13 15:22:42at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
2022-09-13T15:22:42.3973193Z Sep 13 15:22:42at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
2022-09-13T15:22:42.3973857Z Sep 13 15:22:42at 
org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
2022-09-13T15:22:42.3974634Z Sep 13 15:22:42at 
org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
2022-09-13T15:22:42.3975420Z Sep 13 15:22:42at 
org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
2022-09-13T15:22:42.3976060Z Sep 13 15:22:42at 
org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
2022-09-13T15:22:42.3976689Z Sep 13 15:22:42at 
org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
2022-09-13T15:22:42.3977555Z Sep 13 15:22:42at 
org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
2022-09-13T15:22:42.3978248Z Sep 13 15:22:42at 
org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
2022-09-13T15:22:42.3978856Z Sep 13 15:22:42at 
org.junit.rules.RunRules.evaluate(RunRules.java:20)
2022-09-13T15:22:42.3979696Z Sep 13 15:22:42at 
org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
2022-09-13T15:22:42.3980716Z Sep 13 15:22:42at 
org.junit.runners.ParentRunner.run(ParentRunner.java:413)
2022-09-13T15:22:42.3981785Z Sep 13 15:22:42at 
org.junit.runner.JUnitCore.run(JUnitCore.java:137)
2022-09-13T15:22:42.3982352Z Sep 13 15:22:42at 
org.junit.runner.JUnitCore.run(JUnitCore.java:115)
2022-09-13T15:22:42.398298

[SUMMARY] Flink 1.16 release sync of 2022-09-13

[Xingbo Huang]

I would like to give you a brief update of the Flink 1.16 release sync
meating of 2022-09-13.

*We have finished x-team testing and all blocker issues have been fixed, so
we will start to prepare rc0*

*We still have some critical test stabilities[1] need to be resolved*

For more information about Flink release 1.16, you can refer to
https://cwiki.apache.org/confluence/display/FLINK/1.16+Release

The next Flink release sync will be on Tuesday the 20th of September at 9am
CEST/ 3pm China Standard Time / 7am UTC. The link could be found on the
following page
https://cwiki.apache.org/confluence/display/FLINK/1.16+Release#id-1.16Release-Syncmeeting
.

On behalf of all the release managers,

best regards,
Xingbo

[1]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLINK%20AND%20issuetype%20%3D%20Bug%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20priority%20in%20(Blocker%2C%20Critical)%20AND%20fixVersion%20%3D%201.16.0%20ORDER%20BY%20summary%20ASC%2C%20priority%20DESC

[jira] [Created] (FLINK-29274) HiveServer2EndpointITCase.testGetFunctionWithPattern failed with Persistence Manager has been closed

[Xingbo Huang (Jira)]

Xingbo Huang created FLINK-29274:


 Summary: HiveServer2EndpointITCase.testGetFunctionWithPattern 
failed with Persistence Manager has been closed
 Key: FLINK-29274
 URL: https://issues.apache.org/jira/browse/FLINK-29274
 Project: Flink
  Issue Type: Bug
  Components: Connectors / Hive
Affects Versions: 1.16.0
Reporter: Xingbo Huang
 Fix For: 1.16.0


{code:java}
4.6807800Z Sep 13 02:07:54 [ERROR] 
org.apache.flink.table.endpoint.hive.HiveServer2EndpointITCase.testGetFunctionWithPattern
  Time elapsed: 22.127 s  <<< ERROR!
2022-09-13T02:07:54.6813586Z Sep 13 02:07:54 java.sql.SQLException: 
javax.jdo.JDOFatalUserException: Persistence Manager has been closed
2022-09-13T02:07:54.6815315Z Sep 13 02:07:54at 
org.apache.hive.jdbc.HiveStatement.waitForOperationToComplete(HiveStatement.java:401)
2022-09-13T02:07:54.6816917Z Sep 13 02:07:54at 
org.apache.hive.jdbc.HiveStatement.execute(HiveStatement.java:266)
2022-09-13T02:07:54.6818338Z Sep 13 02:07:54at 
org.apache.flink.table.endpoint.hive.HiveServer2EndpointITCase.lambda$testGetFunctionWithPattern$29(HiveServer2EndpointITCase.java:542)
2022-09-13T02:07:54.6819988Z Sep 13 02:07:54at 
org.apache.flink.table.endpoint.hive.HiveServer2EndpointITCase.runGetObjectTest(HiveServer2EndpointITCase.java:633)
2022-09-13T02:07:54.6821484Z Sep 13 02:07:54at 
org.apache.flink.table.endpoint.hive.HiveServer2EndpointITCase.runGetObjectTest(HiveServer2EndpointITCase.java:621)
2022-09-13T02:07:54.6823318Z Sep 13 02:07:54at 
org.apache.flink.table.endpoint.hive.HiveServer2EndpointITCase.testGetFunctionWithPattern(HiveServer2EndpointITCase.java:539)
2022-09-13T02:07:54.6824711Z Sep 13 02:07:54at 
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
2022-09-13T02:07:54.6825817Z Sep 13 02:07:54at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
2022-09-13T02:07:54.6827003Z Sep 13 02:07:54at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
2022-09-13T02:07:54.6828259Z Sep 13 02:07:54at 
java.lang.reflect.Method.invoke(Method.java:498)
2022-09-13T02:07:54.6829478Z Sep 13 02:07:54at 
org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:725)
2022-09-13T02:07:54.6830717Z Sep 13 02:07:54at 
org.junit.jupiter.engine.execution.MethodInvocation.proceed(MethodInvocation.java:60)
2022-09-13T02:07:54.6832444Z Sep 13 02:07:54at 
org.junit.jupiter.engine.execution.InvocationInterceptorChain$ValidatingInvocation.proceed(InvocationInterceptorChain.java:131)
2022-09-13T02:07:54.6834028Z Sep 13 02:07:54at 
org.junit.jupiter.engine.extension.TimeoutExtension.intercept(TimeoutExtension.java:149)
2022-09-13T02:07:54.6835304Z Sep 13 02:07:54at 
org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestableMethod(TimeoutExtension.java:140)
2022-09-13T02:07:54.6836734Z Sep 13 02:07:54at 
org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestMethod(TimeoutExtension.java:84)
2022-09-13T02:07:54.6838257Z Sep 13 02:07:54at 
org.junit.jupiter.engine.execution.ExecutableInvoker$ReflectiveInterceptorCall.lambda$ofVoidMethod$0(ExecutableInvoker.java:115)
2022-09-13T02:07:54.6839775Z Sep 13 02:07:54at 
org.junit.jupiter.engine.execution.ExecutableInvoker.lambda$invoke$0(ExecutableInvoker.java:105)
2022-09-13T02:07:54.6841400Z Sep 13 02:07:54at 
org.junit.jupiter.engine.execution.InvocationInterceptorChain$InterceptedInvocation.proceed(InvocationInterceptorChain.java:106)
2022-09-13T02:07:54.6843309Z Sep 13 02:07:54at 
org.junit.jupiter.engine.execution.InvocationInterceptorChain.proceed(InvocationInterceptorChain.java:64)
2022-09-13T02:07:54.6845300Z Sep 13 02:07:54at 
org.junit.jupiter.engine.execution.InvocationInterceptorChain.chainAndInvoke(InvocationInterceptorChain.java:45)
2022-09-13T02:07:54.6846879Z Sep 13 02:07:54at 
org.junit.jupiter.engine.execution.InvocationInterceptorChain.invoke(InvocationInterceptorChain.java:37)
2022-09-13T02:07:54.6848406Z Sep 13 02:07:54at 
org.junit.jupiter.engine.execution.ExecutableInvoker.invoke(ExecutableInvoker.java:104)
2022-09-13T02:07:54.6849760Z Sep 13 02:07:54at 
org.junit.jupiter.engine.execution.ExecutableInvoker.invoke(ExecutableInvoker.java:98)
2022-09-13T02:07:54.6851297Z Sep 13 02:07:54at 
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.lambda$invokeTestMethod$7(TestMethodTestDescriptor.java:214)
2022-09-13T02:07:54.6853032Z Sep 13 02:07:54at 
org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
2022-09-13T02:07:54.6854384Z Sep 13 02:07:54at 
org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.invokeTestMethod(TestMethodTestDescriptor.java:210)
2022-09-13T02:07:54.6856052Z Sep 13

[VOTE] Release 1.14.6, release candidate #2

[Xingbo Huang]

Hi everyone,

Please review and vote on the release candidate #2 for the version 1.14.6,
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],
* the official Apache source release and binary convenience releases to be
deployed to dist.apache.org [2], which are signed with the key with
fingerprint 3C2C9FFB59DF9F3E [3],
* all artifacts to be deployed to the Maven Central Repository [4],
* source code tag "release-1.14.6-rc2" [5],
* website pull request listing the new release and adding announcement blog
post [6].

The vote will be open for at least 72 hours. It is adopted by majority
approval, with at least 3 PMC affirmative votes.

Best,
Xingbo

[1]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12351834
[2] https://dist.apache.org/repos/dist/dev/flink/flink-1.14.6-rc2/
[3] https://dist.apache.org/repos/dist/release/flink/KEYS
[4] https://repository.apache.org/content/repositories/orgapacheflink-1531/
[5] https://github.com/apache/flink/tree/release-1.14.6-rc2
[6] https://github.com/apache/flink-web/pull/569

Re: [ANNOUNCE] New Apache Flink PMC Member - Martijn Visser

[Xingbo Huang]

Congratulations, Martijn!
Well deserved.

Best,
Xingbo

Geng Biao  于2022年9月10日周六 18:38写道：

> Congrats, Martijn!
> Best,
> Biao
>
> 获取 Outlook for iOS
> 
> 发件人: Sergey Nuyanzin 
> 发送时间: Saturday, September 10, 2022 6:10:01 PM
> 收件人: dev@flink.apache.org 
> 主题: Re: [ANNOUNCE] New Apache Flink PMC Member - Martijn Visser
>
> Congratulations, Martijn!
> Well deserved.
>
> On Fri, Sep 9, 2022 at 6:38 PM Matthias Pohl  .invalid>
> wrote:
>
> > Congrats, Martijn! Indeed, well deserved :-)
> >
> > On Fri, Sep 9, 2022 at 5:10 PM tison  wrote:
> >
> > > Congrats! Well deserved.
> > >
> > > Best,
> > > tison.
> > >
> > >
> > > Timo Walther  于2022年9月9日周五 23:08写道：
> > >
> > > > Hi everyone,
> > > >
> > > > I'm very happy to announce that Martijn Visser has joined the Flink
> > PMC!
> > > >
> > > > Martijn has helped the community in many different ways over the past
> > > > months. Externalizing the connectors from the Flink repo to their own
> > > > repository, continously updating dependencies, and performing other
> > > > project-wide refactorings. He is constantly coordinating
> contributions,
> > > > connecting stakeholders, finding committers for contributions,
> driving
> > > > release syncs, and helping in making the ASF a better place (e.g. by
> > > > using Matomo an ASF-compliant tracking solution for all projects).
> > > >
> > > > Congratulations and welcome, Martijn!
> > > >
> > > > Cheers,
> > > > Timo Walther
> > > > (On behalf of the Apache Flink PMC)
> > > >
> > >
> >
>
>
> --
> Best regards,
> Sergey
>

Re: [SUMMARY] Flink 1.16 release sync of 2022-09-06

[Xingbo Huang]

Hi tison,

Thanks for the information. I think the pr is a bug fix, so it is fine to
merge into the release branch. We are now waiting for three blocker issues
to be resolved. After that we will prepare rc0.

Best,
Xingbo

tison  于2022年9月9日周五 17:07写道：

> Hi Xingbo,
>
> I just notice that 1.16.0 didn't release yet after I merge
> https://github.com/apache/flink/pull/20798 into the release branch. Sorry
> for making this change.
>
> This is a trivial change but if you'd like to revert it, please do it and
> comment in the original PR.
>
> Best,
> tison.
>
>
> Xingbo Huang  于2022年9月6日周二 16:09写道：
>
> > I would like to give you a brief update of the Flink 1.16 release sync
> > meating of 2022-09-06.
> >
> > *We have cut release-1.16 branch yesterday(5th of September 2022). It is
> > expected that we will prepare rc0 for further testing in a few days*
> >
> > *We're almost done with x-team testing[1]. The remaining test issues are
> > also expected to be finished in the next two days.*
> >
> > *Currently, there are 4 blocker issues which are being worked on. Many
> > thanks to these contributors and reviewers.
> > - FLINK-29120 <https://issues.apache.org/jira/browse/FLINK-29120>,
> > FLINK-28975 <https://issues.apache.org/jira/browse/FLINK-28975>,
> > FLINK-28941
> > <https://issues.apache.org/jira/browse/FLINK-28941>, FLINK-29196
> > <https://issues.apache.org/jira/browse/FLINK-29196>
> >
> > *We have finished the license check and only found a license problem*
> >
> > *We still have some critical test stabilities[2] need to be resolved*
> >
> > For more information about Flink release 1.16, you can refer to
> > https://cwiki.apache.org/confluence/display/FLINK/1.16+Release
> >
> > The next Flink release sync will be on Tuesday the 13th of September at
> 9am
> > CEST/ 3pm China Standard Time / 7am UTC. The link could be found on the
> > following page
> >
> >
> https://cwiki.apache.org/confluence/display/FLINK/1.16+Release#id-1.16Release-Syncmeeting
> > .
> >
> > On behalf of all the release managers,
> >
> > best regards,
> > Xingbo
> >
> > [1] https://issues.apache.org/jira/browse/FLINK-28896
> > [2]
> >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLINK%20AND%20issuetype%20%3D%20Bug%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20priority%20in%20(Blocker%2C%20Critical)%20AND%20fixVersion%20%3D%201.16.0%20ORDER%20BY%20summary%20ASC%2C%20priority%20DESC
> >
>

Re: [VOTE] Release 1.14.6, release candidate #1

[Xingbo Huang]

Thanks Jingsong for the check. My mac hung for some minutes due to network
problems during building, which may have caused the incomplete package. The
RC1 would be canceled and I'll create the RC2 asap.

Best,
Xingbo

Jingsong Li  于2022年9月9日周五 12:17写道：

> -1
>
> shasum -a 512 flink-1.14.6-bin-scala_2.11.tgz
>
> 33d55347e93369164b166a54cd1625d617f3df92f5f788d87778c36bb7b2b7bc64d565d87f25c4fcb5f3c70ffa96fc89f9a774143459a6d810667534db1cd695
>  flink-1.14.6-bin-scala_2.11.tgz
>
> cat flink-1.14.6-bin-scala_2.11.tgz.sha512
>
> a2b1cac32778272c1741befa79832056d07977f9b714edccea9c1fdd7f73ba711beb5013c3b5f2794d53f74c3cfcfd19cc3145d86b17644a083edca4be0a4258
>  flink-1.14.6-bin-scala_2.11.tgz
>
> Looks like the sha is not correct.
>
> Best,
> Jingsong
>
> On Fri, Sep 9, 2022 at 9:56 AM Xingbo Huang  wrote:
> >
> > Hi everyone,
> >
> > Please review and vote on the release candidate #1 for the version
> 1.14.6,
> > 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],
> > * the official Apache source release and binary convenience releases to
> be
> > deployed to dist.apache.org [2], which are signed with the key with
> > fingerprint 3C2C9FFB59DF9F3E [3],
> > * all artifacts to be deployed to the Maven Central Repository [4],
> > * source code tag "release-1.14.6-rc1" [5],
> > * website pull request listing the new release and adding announcement
> blog
> > post [6].
> >
> > The vote will be open for at least 72 hours. It is adopted by majority
> > approval, with at least 3 PMC affirmative votes.
> >
> > Best,
> > Xingbo
> >
> > [1]
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12351834
> > [2] https://dist.apache.org/repos/dist/dev/flink/flink-1.14.6-rc1/
> > [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> > [4]
> https://repository.apache.org/content/repositories/orgapacheflink-1529/
> > [5] https://github.com/apache/flink/tree/release-1.14.6-rc1
> > [6] https://github.com/apache/flink-web/pull/569
>

Re: [ANNOUNCE] New Apache Flink Committer - Caizhi Weng

[Xingbo Huang]

Congratulations Caizhi

Best,
Xingbo

Jingsong Lee  于2022年9月9日周五 09:41写道：

> Hi everyone,
>
> On behalf of the PMC, I'm very happy to announce Caizhi Weng as a new
> Flink committer.
>
> Caizhi has been contributing to the Flink project for more than 3
> years, and has authored 150+ PRs. He is one of the key driving members
> of the Flink Table Store subproject. He is responsible for the core
> design of transaction committing. Expanded the Hive ecosystem of Flink
> Table Store. He also works in Flink SQL, helps solve the problems of
> ease of use and performance.
>
> Please join me in congratulating Caizhi for becoming a Flink committer!
>
> Best,
> Jingsong
>

[VOTE] Release 1.14.6, release candidate #1

[Xingbo Huang]

Hi everyone,

Please review and vote on the release candidate #1 for the version 1.14.6,
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],
* the official Apache source release and binary convenience releases to be
deployed to dist.apache.org [2], which are signed with the key with
fingerprint 3C2C9FFB59DF9F3E [3],
* all artifacts to be deployed to the Maven Central Repository [4],
* source code tag "release-1.14.6-rc1" [5],
* website pull request listing the new release and adding announcement blog
post [6].

The vote will be open for at least 72 hours. It is adopted by majority
approval, with at least 3 PMC affirmative votes.

Best,
Xingbo

[1]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12351834
[2] https://dist.apache.org/repos/dist/dev/flink/flink-1.14.6-rc1/
[3] https://dist.apache.org/repos/dist/release/flink/KEYS
[4] https://repository.apache.org/content/repositories/orgapacheflink-1529/
[5] https://github.com/apache/flink/tree/release-1.14.6-rc1
[6] https://github.com/apache/flink-web/pull/569

Re: [DISCUSS] Releasing Flink 1.14.6

[Xingbo Huang]

Thanks everyone,

I will start with the preparation for the release.

Best,
Xingbo

Yu Li  于2022年9月8日周四 11:19写道：

> +1
>
> Best Regards,
> Yu
>
>
> On Tue, 6 Sept 2022 at 17:57, Xintong Song  wrote:
>
> > +1
> >
> > Best,
> >
> > Xintong
> >
> >
> >
> > On Tue, Sep 6, 2022 at 5:55 PM Konstantin Knauf 
> wrote:
> >
> > > Sounds good. +1.
> > >
> > > Am Di., 6. Sept. 2022 um 10:45 Uhr schrieb Jingsong Li <
> > > jingsongl...@gmail.com>:
> > >
> > > > +1 for 1.14.6
> > > >
> > > > Thanks Xingbo for driving.
> > > >
> > > > Best,
> > > > Jingsong
> > > >
> > > > On Tue, Sep 6, 2022 at 4:42 PM Xingbo Huang 
> > wrote:
> > > > >
> > > > > Hi all,
> > > > >
> > > > > I would like to start discussing releasing Flink 1.14.6.
> > > > >
> > > > > It has already been almost three months since we released 1.14.5.
> > There
> > > > are
> > > > > currently 35 tickets[1] and 33 commits[2] already resolved for
> > 1.14.6,
> > > > some
> > > > > of them quite important, such as FLINK-27399
> > > > > <https://issues.apache.org/jira/browse/FLINK-27399> and
> FLINK-29138
> > > > > <https://issues.apache.org/jira/browse/FLINK-29138>.
> > > > >
> > > > > Currently, there are no issues marked as critical or blocker for
> > > 1.14.6.
> > > > > Please let me know if there are any issues you'd like to be
> included
> > in
> > > > > this release but still not merged.
> > > > >
> > > > > I would like to volunteer as a release manager for 1.14.6, and
> start
> > > the
> > > > > release process once all the issues are merged.
> > > > >
> > > > > Best,
> > > > > Xingbo
> > > > >
> > > > > [1]
> > > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLINK%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%201.14.6
> > > > > [2]
> > > >
> https://github.com/apache/flink/compare/release-1.14.5...release-1.14
> > > >
> > >
> > >
> > > --
> > > https://twitter.com/snntrable
> > > https://github.com/knaufk
> > >
> >
>

[jira] [Created] (FLINK-29220) Skip ci tests on docs-only-PRs

[Xingbo Huang (Jira)]

Xingbo Huang created FLINK-29220:


 Summary: Skip ci tests on docs-only-PRs
 Key: FLINK-29220
 URL: https://issues.apache.org/jira/browse/FLINK-29220
 Project: Flink
  Issue Type: Improvement
  Components: Build System / Azure Pipelines
Affects Versions: 1.16.0
Reporter: Xingbo Huang


For the docs-only-PRs, we can skip the ci tests. But there is an exception 
here, if the content of `static/generated` or `layouts/shortcodes/generated` is 
modified, we also need to trigger the ci tests, which can prevent that the doc 
of config or rest api has been changed, but the corresponding code is not 
together changed



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (FLINK-29217) CoordinatorEventsToStreamOperatorRecipientExactlyOnceITCase.testConcurrentCheckpoint failed with AssertionFailedError

[Xingbo Huang (Jira)]

Xingbo Huang created FLINK-29217:


 Summary: 
CoordinatorEventsToStreamOperatorRecipientExactlyOnceITCase.testConcurrentCheckpoint
 failed with AssertionFailedError
 Key: FLINK-29217
 URL: https://issues.apache.org/jira/browse/FLINK-29217
 Project: Flink
  Issue Type: Bug
  Components: Runtime / Checkpointing
Affects Versions: 1.16.0
Reporter: Xingbo Huang
 Fix For: 1.16.0


{code:java}
2022-09-07T02:00:50.2507464Z Sep 07 02:00:50 [ERROR] 
org.apache.flink.streaming.runtime.tasks.CoordinatorEventsToStreamOperatorRecipientExactlyOnceITCase.testConcurrentCheckpoint
  Time elapsed: 2.137 s  <<< FAILURE!
2022-09-07T02:00:50.2508673Z Sep 07 02:00:50 
org.opentest4j.AssertionFailedError: 
2022-09-07T02:00:50.2509309Z Sep 07 02:00:50 
2022-09-07T02:00:50.2509945Z Sep 07 02:00:50 Expecting value to be false but 
was true
2022-09-07T02:00:50.2511950Z Sep 07 02:00:50at 
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
2022-09-07T02:00:50.2513254Z Sep 07 02:00:50at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
2022-09-07T02:00:50.2514621Z Sep 07 02:00:50at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
2022-09-07T02:00:50.2516342Z Sep 07 02:00:50at 
org.apache.flink.streaming.runtime.tasks.CoordinatorEventsToStreamOperatorRecipientExactlyOnceITCase.testConcurrentCheckpoint(CoordinatorEventsToStreamOperatorRecipientExactlyOnceITCase.java:173)
2022-09-07T02:00:50.2517852Z Sep 07 02:00:50at 
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
2022-09-07T02:00:50.251Z Sep 07 02:00:50at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
2022-09-07T02:00:50.2520065Z Sep 07 02:00:50at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
2022-09-07T02:00:50.2521153Z Sep 07 02:00:50at 
java.lang.reflect.Method.invoke(Method.java:498)
2022-09-07T02:00:50.2522747Z Sep 07 02:00:50at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
2022-09-07T02:00:50.2523973Z Sep 07 02:00:50at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
2022-09-07T02:00:50.2525158Z Sep 07 02:00:50at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
2022-09-07T02:00:50.2526347Z Sep 07 02:00:50at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
2022-09-07T02:00:50.2527525Z Sep 07 02:00:50at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
2022-09-07T02:00:50.2528646Z Sep 07 02:00:50at 
org.apache.flink.util.TestNameProvider$1.evaluate(TestNameProvider.java:45)
2022-09-07T02:00:50.2529708Z Sep 07 02:00:50at 
org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:61)
2022-09-07T02:00:50.2530744Z Sep 07 02:00:50at 
org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
2022-09-07T02:00:50.2532008Z Sep 07 02:00:50at 
org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
2022-09-07T02:00:50.2533137Z Sep 07 02:00:50at 
org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
2022-09-07T02:00:50.2544265Z Sep 07 02:00:50at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
2022-09-07T02:00:50.2545595Z Sep 07 02:00:50at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
2022-09-07T02:00:50.2546782Z Sep 07 02:00:50at 
org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
2022-09-07T02:00:50.2547810Z Sep 07 02:00:50at 
org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
2022-09-07T02:00:50.2548890Z Sep 07 02:00:50at 
org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
2022-09-07T02:00:50.2549932Z Sep 07 02:00:50at 
org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
2022-09-07T02:00:50.2550933Z Sep 07 02:00:50at 
org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
2022-09-07T02:00:50.2552325Z Sep 07 02:00:50at 
org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:54)
2022-09-07T02:00:50.2553660Z Sep 07 02:00:50at 
org.junit.rules.RunRules.evaluate(RunRules.java:20)
2022-09-07T02:00:50.2554661Z Sep 07 02:00:50at 
org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
2022-09-07T02:00:50.290Z Sep 07 02:00:50at 
org.junit.runners.ParentRunner.run(ParentRunner.java:413)
2022-09-07T02:00:50.2556454Z Sep 07 02:00:50at 
org.junit.runner.JUnitCore.run(JUnitCore.java:137)
2022-09-07T02:00:50.2557291Z Sep 07 02:00:50at 
org.junit.runner.JUnitCore.run(JUnitCore.java:115)
2022-09-07T02:00:50.2558317Z Sep 07

Re: [VOTE] FLIP-258 Guarantee binary compatibility for Public/-Evolving APIs between patch releases​

[Xingbo Huang]

Thanks Chesnay for driving this,

+1

Best,
Xingbo

Xintong Song  于2022年9月6日周二 17:57写道：

> +1
>
> Best,
>
> Xintong
>
>
>
> On Tue, Sep 6, 2022 at 5:55 PM Konstantin Knauf  wrote:
>
> > +1. Thanks, Chesnay.
> >
> > Am Di., 6. Sept. 2022 um 11:51 Uhr schrieb Chesnay Schepler <
> > ches...@apache.org>:
> >
> > > Since no one objected in the discuss thread, let's vote!
> > >
> > > FLIP:
> > >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=225152857
> > >
> > > The vote will be open for at least 72h.
> > >
> > > Regards,
> > > Chesnay
> > >
> >
> >
> > --
> > https://twitter.com/snntrable
> > https://github.com/knaufk
> >
>

[DISCUSS] Releasing Flink 1.14.6

[Xingbo Huang]

Hi all,

I would like to start discussing releasing Flink 1.14.6.

It has already been almost three months since we released 1.14.5. There are
currently 35 tickets[1] and 33 commits[2] already resolved for 1.14.6, some
of them quite important, such as FLINK-27399
 and FLINK-29138
.

Currently, there are no issues marked as critical or blocker for 1.14.6.
Please let me know if there are any issues you'd like to be included in
this release but still not merged.

I would like to volunteer as a release manager for 1.14.6, and start the
release process once all the issues are merged.

Best,
Xingbo

[1]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLINK%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%201.14.6
[2] https://github.com/apache/flink/compare/release-1.14.5...release-1.14

[SUMMARY] Flink 1.16 release sync of 2022-09-06

[Xingbo Huang]

I would like to give you a brief update of the Flink 1.16 release sync
meating of 2022-09-06.

*We have cut release-1.16 branch yesterday(5th of September 2022). It is
expected that we will prepare rc0 for further testing in a few days*

*We're almost done with x-team testing[1]. The remaining test issues are
also expected to be finished in the next two days.*

*Currently, there are 4 blocker issues which are being worked on. Many
thanks to these contributors and reviewers.
- FLINK-29120 ,
FLINK-28975 , FLINK-28941
, FLINK-29196


*We have finished the license check and only found a license problem*

*We still have some critical test stabilities[2] need to be resolved*

For more information about Flink release 1.16, you can refer to
https://cwiki.apache.org/confluence/display/FLINK/1.16+Release

The next Flink release sync will be on Tuesday the 13th of September at 9am
CEST/ 3pm China Standard Time / 7am UTC. The link could be found on the
following page
https://cwiki.apache.org/confluence/display/FLINK/1.16+Release#id-1.16Release-Syncmeeting
.

On behalf of all the release managers,

best regards,
Xingbo

[1] https://issues.apache.org/jira/browse/FLINK-28896
[2]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLINK%20AND%20issuetype%20%3D%20Bug%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20priority%20in%20(Blocker%2C%20Critical)%20AND%20fixVersion%20%3D%201.16.0%20ORDER%20BY%20summary%20ASC%2C%20priority%20DESC

[jira] [Created] (FLINK-29196) Check 1.16 licensing

[Xingbo Huang (Jira)]

Xingbo Huang created FLINK-29196:


 Summary: Check 1.16 licensing
 Key: FLINK-29196
 URL: https://issues.apache.org/jira/browse/FLINK-29196
 Project: Flink
  Issue Type: Technical Debt
  Components: Release System
Affects Versions: 1.16.0
Reporter: Xingbo Huang
 Fix For: 1.16.0


We should check the licensing of the 1.16 release.

[https://cwiki.apache.org/confluence/display/FLINK/Licensing]

 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[ANNOUNCE] release-1.16 branch cut

[Xingbo Huang]

Hi devs,

The release-1.16 branch has been forked out from the master branch, at the
commit 4b15bc900eb60b1830bc406975ce974ad6050f98. Also, the version
on the master branch has been upgraded to 1.17-SNAPSHOT.

>From now on, for PRs that should be presented in 1.16.0, please make sure:
- Merge the PR into both master and release-1.16 branches
- The JIRA ticket should be closed with the correct fix-versions (1.16.0).

Thank you~
Chesnay, Martjin, Godfrey & Xingbo

Re: [DISCUSS] Switch docker iamge base to Eclipse Temurin

[Xingbo Huang]

Thanks Chesnay for driving this. I found a problem with image name
change[1] and I have created a PR[2] to fix it.

Best,
Xingbo

[1] https://issues.apache.org/jira/browse/FLINK-29161
[2] https://github.com/apache/flink/pull/20726

Chesnay Schepler  于2022年8月31日周三 17:15写道：

> I will optimistically merge the PRs that make the switch so we can
> gather some e2e testing data.
>
> On 30/08/2022 14:51, Chesnay Schepler wrote:
> > yes, alpine would have similar issues as CentOS. As for usability,
> > from personal experience it has always been a bit of a drag to extend
> > or use manually because it is such a minimal image.
> >
> > On 30/08/2022 14:45, Matthias Pohl wrote:
> >> Thanks for bringing this up, Chesnay. Can you elaborate a bit more on
> >> what
> >> you mean when referring to Alpine as being "not as user-friendly"?
> >> Doesn't
> >> it come with the same issue that switching to CentOS comes with that we
> >> have to update our scripts (I'm thinking of apt in particular)? Or what
> >> else did you have in mind in terms of user-friendliness? I would imagine
> >> selecting the required packages would be a bit more tedious.
> >>
> >> I'm wondering whether we considered the security aspect. A more minimal
> >> Alpine base image might reduce the risk of running into CVEs. But then;
> >> it's also the question how fast those CVEs are actually fixed on average
> >> (now comparing Ubuntu and Alpine for instance). Or is this even a
> >> concern
> >> for us?
> >>
> >> I didn't find any clear answers around that topic with a quick Google
> >> search. [1] was kind of interesting to read.
> >>
> >> Anyway, I definitely see the benefits of just switching to Ubuntu due to
> >> the fact that it also relies on Debian's package management (reducing
> >> the
> >> migration effort) and that we're using it for our CI builds
> >> (consistency).
> >>
> >> +1 for going with Ubuntu if security is not a big concern
> >>
> >> Best,
> >> Matthias
> >>
> >> [1]
> >>
> https://jfrog.com/knowledge-base/why-use-ubuntu-as-a-docker-base-image-when-alpine-exists/
> >>
> >>
> >> On Tue, Aug 30, 2022 at 11:40 AM Chesnay Schepler 
> >> wrote:
> >>
> >>> Hello,
> >>>
> >>> during the release of the 1.15.2 images
> >>>  it was
> >>> noted that we use the openjdk:8/11 images, which have been deprecated
> >>>  and thus no
> >>> longer receive any updates.
> >>>
> >>> There are a number of alternatives, the most promising being Eclipse
> >>> Temurin , the successor of
> >>> AdoptOpenJDK, since it's vendor neutral.
> >>>
> >>> This would imply a switch of distros from Debian to most likely Ubuntu
> >>> 22.04 (Alpine isn't as user-friendly, and CentOS is likely incompatible
> >>> with existing images using our images as a base). We are also running
> >>> our CI on Ubuntu, so I don't expect any issues.
> >>>
> >>> Let me know what you think.
> >>>
> >>> The required changes on our side appear to be minimal; I have already
> >>> prepared a PR .
> >>>
> >
>
>

[jira] [Created] (FLINK-29161) Run kubernetes application HA test failed with unable to prepare context: path "dev/test_kubernetes_application_ha-debian" not found

[Xingbo Huang (Jira)]

Xingbo Huang created FLINK-29161:


 Summary: Run kubernetes application HA test failed with unable to 
prepare context: path "dev/test_kubernetes_application_ha-debian" not found
 Key: FLINK-29161
 URL: https://issues.apache.org/jira/browse/FLINK-29161
 Project: Flink
  Issue Type: Technical Debt
  Components: Build System / Azure Pipelines
Affects Versions: 1.16.0
Reporter: Xingbo Huang
 Fix For: 1.16.0


{code:java}
2022-08-31T09:13:50.8050601Z Aug 31 09:13:50 Preparing Dockeriles
2022-08-31T09:13:50.8051483Z Aug 31 09:13:50 Executing command: git clone 
https://github.com/apache/flink-docker.git --branch dev-master --single-branch
2022-08-31T09:13:50.8069617Z Cloning into 'flink-docker'...
2022-08-31T09:13:51.4728169Z Generating Dockerfiles... done.
2022-08-31T09:13:51.4732889Z Aug 31 09:13:51 Building images
2022-08-31T09:13:51.5013231Z unable to prepare context: path 
"dev/test_kubernetes_application_ha-debian" not found
2022-08-31T09:13:51.5041357Z Aug 31 09:13:51 ~/work/1/s/cri-dockerd
2022-08-31T09:13:51.5042427Z Aug 31 09:13:51 Command: build_image 
test_kubernetes_application_ha 10.1.0.160 failed. Retrying...
2022-08-31T09:13:53.5058625Z Aug 31 09:13:53 Starting fileserver for Flink 
distribution
2022-08-31T09:13:53.5060253Z Aug 31 09:13:53 
~/work/1/s/flink-dist/target/flink-1.16-SNAPSHOT-bin ~/work/1/s/cri-dockerd
2022-08-31T09:14:13.8161820Z Aug 31 09:14:13 ~/work/1/s/cri-dockerd
2022-08-31T09:14:13.8164441Z Aug 31 09:14:13 
~/work/1/s/flink-end-to-end-tests/test-scripts/temp-test-directory-06753986230 
~/work/1/s/cri-dockerd
2022-08-31T09:14:13.8165256Z Aug 31 09:14:13 Preparing Dockeriles
2022-08-31T09:14:13.8166118Z Aug 31 09:14:13 Executing command: git clone 
https://github.com/apache/flink-docker.git --branch dev-master --single-branch
2022-08-31T09:14:13.8182037Z fatal: destination path 'flink-docker' already 
exists and is not an empty directory.
2022-08-31T09:14:13.8188942Z Aug 31 09:14:13 Retry 1/5 exited 128, retrying in 
1 seconds...
2022-08-31T09:14:14.1481612Z Traceback (most recent call last):
2022-08-31T09:14:14.1483171Z   File 
"/home/vsts/work/1/s/flink-end-to-end-tests/test-scripts/python3_fileserver.py",
 line 26, in 
2022-08-31T09:14:14.1484572Z httpd = socketserver.TCPServer(("", ), 
handler)
2022-08-31T09:14:14.1485179Z   File "/usr/lib/python3.8/socketserver.py", line 
452, in __init__
2022-08-31T09:14:14.1485724Z self.server_bind()
2022-08-31T09:14:14.1486247Z   File "/usr/lib/python3.8/socketserver.py", line 
466, in server_bind
2022-08-31T09:14:14.1486795Z self.socket.bind(self.server_address)
2022-08-31T09:14:14.1487783Z OSError: [Errno 98] Address already in use {code}
[https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=40556=logs=bea52777-eaf8-5663-8482-18fbc3630e81=b2642e3a-5b86-574d-4c8a-f7e2842bfb14]

 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (FLINK-29155) Improve default config of grpcServer in Process Mode

[Xingbo Huang (Jira)]

Xingbo Huang created FLINK-29155:


 Summary: Improve default config of grpcServer in Process Mode
 Key: FLINK-29155
 URL: https://issues.apache.org/jira/browse/FLINK-29155
 Project: Flink
  Issue Type: Improvement
  Components: API / Python
Affects Versions: 1.15.2, 1.14.5, 1.16.0
Reporter: Xingbo Huang


The existing grpcServer configuration may cause channel disconnection when 
there is a large amount of data. Some PyFlink users are very troubled by this 
problem.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (FLINK-29147) ChangelogLocalRecoveryITCase.testRestartTM failed with CheckpointException

[Xingbo Huang (Jira)]

Xingbo Huang created FLINK-29147:


 Summary: ChangelogLocalRecoveryITCase.testRestartTM failed with 
CheckpointException
 Key: FLINK-29147
 URL: https://issues.apache.org/jira/browse/FLINK-29147
 Project: Flink
  Issue Type: Bug
  Components: Runtime / State Backends
Affects Versions: 1.16.0
Reporter: Xingbo Huang
 Fix For: 1.16.0


{code:java}
2022-08-30T13:30:24.9214696Z Aug 30 13:30:24 [ERROR] 
ChangelogLocalRecoveryITCase.testRestartTM  Time elapsed: 9.056 s  <<< ERROR!
2022-08-30T13:30:24.9235235Z Aug 30 13:30:24 
java.util.concurrent.ExecutionException: 
org.apache.flink.runtime.checkpoint.CheckpointException: Checkpoint triggering 
task Source: Custom Source (1/1) of job 2070563b800eceb80fb9f6cab1da5c00 is not 
being executed at the moment. Aborting checkpoint. Failure reason: Not all 
required tasks are currently running.
2022-08-30T13:30:24.9254389Z Aug 30 13:30:24at 
java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)
2022-08-30T13:30:24.9274122Z Aug 30 13:30:24at 
java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1908)
2022-08-30T13:30:24.9293512Z Aug 30 13:30:24at 
org.apache.flink.test.checkpointing.ChangelogLocalRecoveryITCase.testRestartTM(ChangelogLocalRecoveryITCase.java:145)
2022-08-30T13:30:24.9295187Z Aug 30 13:30:24at 
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
2022-08-30T13:30:24.9304089Z Aug 30 13:30:24at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
2022-08-30T13:30:24.9305377Z Aug 30 13:30:24at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
2022-08-30T13:30:24.9324825Z Aug 30 13:30:24at 
java.lang.reflect.Method.invoke(Method.java:498)
2022-08-30T13:30:24.9326046Z Aug 30 13:30:24at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
2022-08-30T13:30:24.9327330Z Aug 30 13:30:24at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
2022-08-30T13:30:24.9328669Z Aug 30 13:30:24at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
2022-08-30T13:30:24.9329927Z Aug 30 13:30:24at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
2022-08-30T13:30:24.9331480Z Aug 30 13:30:24at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
2022-08-30T13:30:24.9332662Z Aug 30 13:30:24at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
2022-08-30T13:30:24.9426069Z Aug 30 13:30:24at 
org.apache.flink.util.TestNameProvider$1.evaluate(TestNameProvider.java:45)
2022-08-30T13:30:24.9456433Z Aug 30 13:30:24at 
org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:61)
2022-08-30T13:30:24.9475038Z Aug 30 13:30:24at 
org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
2022-08-30T13:30:24.9494771Z Aug 30 13:30:24at 
org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
2022-08-30T13:30:24.9505400Z Aug 30 13:30:24at 
org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
2022-08-30T13:30:24.9506695Z Aug 30 13:30:24at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
2022-08-30T13:30:24.9507972Z Aug 30 13:30:24at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
2022-08-30T13:30:24.9509158Z Aug 30 13:30:24at 
org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
2022-08-30T13:30:24.9510253Z Aug 30 13:30:24at 
org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
2022-08-30T13:30:24.9511548Z Aug 30 13:30:24at 
org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
2022-08-30T13:30:24.9512714Z Aug 30 13:30:24at 
org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
2022-08-30T13:30:24.9513916Z Aug 30 13:30:24at 
org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
2022-08-30T13:30:24.9515034Z Aug 30 13:30:24at 
org.junit.runners.ParentRunner.run(ParentRunner.java:413)
2022-08-30T13:30:24.9516384Z Aug 30 13:30:24at 
org.junit.runners.Suite.runChild(Suite.java:128)
2022-08-30T13:30:24.9517273Z Aug 30 13:30:24at 
org.junit.runners.Suite.runChild(Suite.java:27)
2022-08-30T13:30:24.9518307Z Aug 30 13:30:24at 
org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
2022-08-30T13:30:24.9519469Z Aug 30 13:30:24at 
org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
2022-08-30T13:30:24.9520610Z Aug 30 13:30:24at 
org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
2022-08-30T13:30:24.9521760Z Aug 30 13:30:24at 
org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
2022-08-30T13:30:24.9523124Z Aug 30 13:30:24at 
org.junit.runners.Paren

[SUMMARY] Flink 1.16 release sync of 2022-08-30

[Xingbo Huang]

I would like to give you a brief update of the Flink 1.16 release sync
meating of 2022-08-30.

*Since the feature freeze(9th of August 2022, end of business CEST), we
have started release-testing[1] in the last three weeks. We're almost done
with half of the test issues. The remaining test issues are also expected
to be finished in the next few days.*

*Currently, there are still some critical/blocker stability tickets[2] that
need to be resolved. We will cut 1.16 release branch once our CI is stable
and release-testing work has been finished.*

For more information about Flink release 1.16, you can refer to
https://cwiki.apache.org/confluence/display/FLINK/1.16+Release

The next Flink release sync will be on Tuesday the 6th of September at 9am
CEST/ 3pm China Standard Time / 7am UTC. The link could be found on the
following page
https://cwiki.apache.org/confluence/display/FLINK/1.16+Release#id-1.16Release-Syncmeeting
.

On behalf of all the release managers,

best regards,
Xingbo

[1] https://issues.apache.org/jira/browse/FLINK-28896
[2]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLINK%20AND%20issuetype%20%3D%20Bug%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20priority%20in%20(Blocker%2C%20Critical)%20AND%20fixVersion%20%3D%201.16.0%20ORDER%20BY%20summary%20ASC%2C%20priority%20DESC

[jira] [Created] (FLINK-29105) KubernetesStateHandleStoreTest.testAddAndLockShouldNotThrowAlreadyExistExceptionWithSameContents failed with AssertionFailedError

[Xingbo Huang (Jira)]

Xingbo Huang created FLINK-29105:


 Summary: 
KubernetesStateHandleStoreTest.testAddAndLockShouldNotThrowAlreadyExistExceptionWithSameContents
 failed with AssertionFailedError
 Key: FLINK-29105
 URL: https://issues.apache.org/jira/browse/FLINK-29105
 Project: Flink
  Issue Type: Bug
  Components: Deployment / Kubernetes
Affects Versions: 1.16.0
Reporter: Xingbo Huang
 Fix For: 1.16.0


{code:java}
2022-08-25T04:19:22.1429302Z Aug 25 04:19:22 [ERROR] Tests run: 25, Failures: 
1, Errors: 0, Skipped: 0, Time elapsed: 0.827 s <<< FAILURE! - in 
org.apache.flink.kubernetes.highavailability.KubernetesStateHandleStoreTest
2022-08-25T04:19:22.1447098Z Aug 25 04:19:22 [ERROR] 
org.apache.flink.kubernetes.highavailability.KubernetesStateHandleStoreTest.testAddAndLockShouldNotThrowAlreadyExistExceptionWithSameContents
  Time elapsed: 0.031 s  <<< FAILURE!
2022-08-25T04:19:22.1447862Z Aug 25 04:19:22 
org.opentest4j.AssertionFailedError: 
2022-08-25T04:19:22.1448236Z Aug 25 04:19:22 
2022-08-25T04:19:22.1448561Z Aug 25 04:19:22 expected: 2
2022-08-25T04:19:22.1448893Z Aug 25 04:19:22  but was: 0
2022-08-25T04:19:22.1449330Z Aug 25 04:19:22at 
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
2022-08-25T04:19:22.1450330Z Aug 25 04:19:22at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
2022-08-25T04:19:22.1451114Z Aug 25 04:19:22at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
2022-08-25T04:19:22.1452006Z Aug 25 04:19:22at 
org.apache.flink.kubernetes.highavailability.KubernetesStateHandleStoreTest.retryWithFirstFailedK8sOperation(KubernetesStateHandleStoreTest.java:1218)
2022-08-25T04:19:22.1452956Z Aug 25 04:19:22at 
org.apache.flink.kubernetes.highavailability.KubernetesStateHandleStoreTest.access$600(KubernetesStateHandleStoreTest.java:59)
2022-08-25T04:19:22.1453863Z Aug 25 04:19:22at 
org.apache.flink.kubernetes.highavailability.KubernetesStateHandleStoreTest$5.lambda$null$0(KubernetesStateHandleStoreTest.java:245)
2022-08-25T04:19:22.1454744Z Aug 25 04:19:22at 
org.apache.flink.kubernetes.kubeclient.TestingFlinkKubeClient.checkAndUpdateConfigMap(TestingFlinkKubeClient.java:182)
2022-08-25T04:19:22.1455619Z Aug 25 04:19:22at 
org.apache.flink.kubernetes.highavailability.KubernetesStateHandleStore.updateConfigMap(KubernetesStateHandleStore.java:634)
2022-08-25T04:19:22.1456553Z Aug 25 04:19:22at 
org.apache.flink.kubernetes.highavailability.KubernetesStateHandleStore.addAndLock(KubernetesStateHandleStore.java:219)
2022-08-25T04:19:22.1457435Z Aug 25 04:19:22at 
org.apache.flink.kubernetes.highavailability.KubernetesStateHandleStoreTest$5.lambda$new$1(KubernetesStateHandleStoreTest.java:258)
2022-08-25T04:19:22.1458482Z Aug 25 04:19:22at 
org.apache.flink.kubernetes.highavailability.KubernetesHighAvailabilityTestBase$Context.runTest(KubernetesHighAvailabilityTestBase.java:107)
2022-08-25T04:19:22.1459383Z Aug 25 04:19:22at 
org.apache.flink.kubernetes.highavailability.KubernetesStateHandleStoreTest$5.(KubernetesStateHandleStoreTest.java:237)
2022-08-25T04:19:22.1460391Z Aug 25 04:19:22at 
org.apache.flink.kubernetes.highavailability.KubernetesStateHandleStoreTest.testAddAndLockShouldNotThrowAlreadyExistExceptionWithSameContents(KubernetesStateHandleStoreTest.java:235)
2022-08-25T04:19:22.1461357Z Aug 25 04:19:22at 
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
2022-08-25T04:19:22.1461965Z Aug 25 04:19:22at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
2022-08-25T04:19:22.1462653Z Aug 25 04:19:22at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
2022-08-25T04:19:22.1463280Z Aug 25 04:19:22at 
java.lang.reflect.Method.invoke(Method.java:498)
2022-08-25T04:19:22.1463903Z Aug 25 04:19:22at 
org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:725)
2022-08-25T04:19:22.1464604Z Aug 25 04:19:22at 
org.junit.jupiter.engine.execution.MethodInvocation.proceed(MethodInvocation.java:60)
2022-08-25T04:19:22.1465397Z Aug 25 04:19:22at 
org.junit.jupiter.engine.execution.InvocationInterceptorChain$ValidatingInvocation.proceed(InvocationInterceptorChain.java:131)
2022-08-25T04:19:22.1466211Z Aug 25 04:19:22at 
org.junit.jupiter.engine.extension.TimeoutExtension.intercept(TimeoutExtension.java:149)
2022-08-25T04:19:22.1466943Z Aug 25 04:19:22at 
org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestableMethod(TimeoutExtension.java:140)
2022-08-25T04:19:22.1467701Z Aug 25 04:19:22at 
org.junit.jupiter.engine.extension.TimeoutExtension.interceptTestMethod(TimeoutExtension.java:84)
2022-08-25T04:19:22.146853

Re: [ANNOUNCE] Apache Flink 1.15.2 released

[Xingbo Huang]

Thanks Danny for driving this release

Best,
Xingbo

Jing Ge  于2022年8月25日周四 05:50写道：

> Thanks Danny for your effort!
>
> Best regards,
> Jing
>
> On Wed, Aug 24, 2022 at 11:43 PM Danny Cranmer 
> wrote:
>
>> The Apache Flink community is very happy to announce the release of
>> Apache Flink 1.15.2, which is the second bugfix release for the Apache
>> Flink 1.15 series.
>>
>> Apache Flink® is an open-source stream processing framework for
>> distributed, high-performing, always-available, and accurate data streaming
>> applications.
>>
>> The release is available for download at:
>> https://flink.apache.org/downloads.html
>>
>> Please check out the release blog post for an overview of the
>> improvements for this bugfix release:
>> https://flink.apache.org/news/2022/08/25/release-1.15.2.html
>>
>> The full release notes are available in Jira:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12351829
>>
>> We would like to thank all contributors of the Apache Flink community who
>> made this release possible!
>>
>> Regards,
>> Danny Cranmer
>>
>

[jira] [Created] (FLINK-29102) ChangelogLocalRecoveryITCase.testRestartTM failed with AssertionFailedError

[Xingbo Huang (Jira)]

Xingbo Huang created FLINK-29102:


 Summary: ChangelogLocalRecoveryITCase.testRestartTM failed with 
AssertionFailedError
 Key: FLINK-29102
 URL: https://issues.apache.org/jira/browse/FLINK-29102
 Project: Flink
  Issue Type: Bug
  Components: Runtime / State Backends
Affects Versions: 1.16.0
Reporter: Xingbo Huang
 Fix For: 1.16.0


{code:java}
2022-08-25T02:10:19.1407131Z Aug 25 02:10:19 [ERROR] Tests run: 3, Failures: 1, 
Errors: 0, Skipped: 0, Time elapsed: 20.126 s <<< FAILURE! - in 
org.apache.flink.test.checkpointing.ChangelogLocalRecoveryITCase
2022-08-25T02:10:19.1410088Z Aug 25 02:10:19 [ERROR] 
ChangelogLocalRecoveryITCase.testRestartTM  Time elapsed: 12.501 s  <<< FAILURE!
2022-08-25T02:10:19.1411734Z Aug 25 02:10:19 
org.opentest4j.AssertionFailedError: Graph is in globally terminal state 
(FAILED)
2022-08-25T02:10:19.1413028Z Aug 25 02:10:19at 
org.junit.jupiter.api.AssertionUtils.fail(AssertionUtils.java:43)
2022-08-25T02:10:19.1414753Z Aug 25 02:10:19at 
org.junit.jupiter.api.Assertions.fail(Assertions.java:146)
2022-08-25T02:10:19.1416077Z Aug 25 02:10:19at 
org.apache.flink.runtime.testutils.CommonTestUtils.lambda$waitForAllTaskRunning$3(CommonTestUtils.java:213)
2022-08-25T02:10:19.1417807Z Aug 25 02:10:19at 
org.apache.flink.runtime.testutils.CommonTestUtils.waitUntilCondition(CommonTestUtils.java:150)
2022-08-25T02:10:19.1419455Z Aug 25 02:10:19at 
org.apache.flink.runtime.testutils.CommonTestUtils.waitUntilCondition(CommonTestUtils.java:144)
2022-08-25T02:10:19.1421184Z Aug 25 02:10:19at 
org.apache.flink.runtime.testutils.CommonTestUtils.waitForAllTaskRunning(CommonTestUtils.java:208)
2022-08-25T02:10:19.1422893Z Aug 25 02:10:19at 
org.apache.flink.test.checkpointing.ChangelogLocalRecoveryITCase.testRestartTM(ChangelogLocalRecoveryITCase.java:149)
2022-08-25T02:10:19.1424381Z Aug 25 02:10:19at 
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
2022-08-25T02:10:19.1425730Z Aug 25 02:10:19at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
2022-08-25T02:10:19.1427428Z Aug 25 02:10:19at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
2022-08-25T02:10:19.1428842Z Aug 25 02:10:19at 
java.lang.reflect.Method.invoke(Method.java:498)
2022-08-25T02:10:19.1430173Z Aug 25 02:10:19at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
2022-08-25T02:10:19.1431683Z Aug 25 02:10:19at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
2022-08-25T02:10:19.1433150Z Aug 25 02:10:19at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
2022-08-25T02:10:19.1434760Z Aug 25 02:10:19at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
2022-08-25T02:10:19.1436296Z Aug 25 02:10:19at 
org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
2022-08-25T02:10:19.1437704Z Aug 25 02:10:19at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
2022-08-25T02:10:19.1439268Z Aug 25 02:10:19at 
org.apache.flink.util.TestNameProvider$1.evaluate(TestNameProvider.java:45)
2022-08-25T02:10:19.1441412Z Aug 25 02:10:19at 
org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:61)
2022-08-25T02:10:19.1442792Z Aug 25 02:10:19at 
org.junit.runners.ParentRunner$3.evaluate(ParentRunner.java:306)
2022-08-25T02:10:19.1444190Z Aug 25 02:10:19at 
org.junit.runners.BlockJUnit4ClassRunner$1.evaluate(BlockJUnit4ClassRunner.java:100)
2022-08-25T02:10:19.1445593Z Aug 25 02:10:19at 
org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:366)
2022-08-25T02:10:19.1446946Z Aug 25 02:10:19at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:103)
2022-08-25T02:10:19.1448568Z Aug 25 02:10:19at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:63)
2022-08-25T02:10:19.1449909Z Aug 25 02:10:19at 
org.junit.runners.ParentRunner$4.run(ParentRunner.java:331)
2022-08-25T02:10:19.1451376Z Aug 25 02:10:19at 
org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:79)
2022-08-25T02:10:19.1452655Z Aug 25 02:10:19at 
org.junit.runners.ParentRunner.runChildren(ParentRunner.java:329)
2022-08-25T02:10:19.1454003Z Aug 25 02:10:19at 
org.junit.runners.ParentRunner.access$100(ParentRunner.java:66)
2022-08-25T02:10:19.1455239Z Aug 25 02:10:19at 
org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:293)
2022-08-25T02:10:19.1456511Z Aug 25 02:10:19at 
org.junit.runners.ParentRunner.run(ParentRunner.java:413)
2022-08-25T02:10:19.1458149Z Aug 25 02:10:19at 
org.junit.runners.Suite.runChild(Suite.java:128)
2022-08-25T02:10:19.1460189Z Aug 25 02:10:19at 
org.junit.runn

[jira] [Created] (FLINK-29093) LookupJoinITCase failed with InternalCompilerException

[Xingbo Huang (Jira)]

Xingbo Huang created FLINK-29093:


 Summary: LookupJoinITCase failed with InternalCompilerException
 Key: FLINK-29093
 URL: https://issues.apache.org/jira/browse/FLINK-29093
 Project: Flink
  Issue Type: Bug
  Components: Table SQL / Runtime
Affects Versions: 1.16.0
Reporter: Xingbo Huang
 Fix For: 1.16.0


{code:java}
2022-08-24T03:45:02.5915521Z Aug 24 03:45:02 
org.apache.flink.runtime.client.JobExecutionException: Job execution failed.
2022-08-24T03:45:02.5916823Z Aug 24 03:45:02at 
org.apache.flink.runtime.jobmaster.JobResult.toJobExecutionResult(JobResult.java:144)
2022-08-24T03:45:02.5919320Z Aug 24 03:45:02at 
org.apache.flink.runtime.minicluster.MiniClusterJobClient.lambda$getJobExecutionResult$3(MiniClusterJobClient.java:141)
2022-08-24T03:45:02.5920833Z Aug 24 03:45:02at 
java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:616)
2022-08-24T03:45:02.5922361Z Aug 24 03:45:02at 
java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:591)
2022-08-24T03:45:02.5923733Z Aug 24 03:45:02at 
java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:488)
2022-08-24T03:45:02.5924922Z Aug 24 03:45:02at 
java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:1975)
2022-08-24T03:45:02.5926191Z Aug 24 03:45:02at 
org.apache.flink.runtime.rpc.akka.AkkaInvocationHandler.lambda$invokeRpc$1(AkkaInvocationHandler.java:268)
2022-08-24T03:45:02.5927677Z Aug 24 03:45:02at 
java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:774)
2022-08-24T03:45:02.5929091Z Aug 24 03:45:02at 
java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:750)
2022-08-24T03:45:02.5930430Z Aug 24 03:45:02at 
java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:488)
2022-08-24T03:45:02.5931966Z Aug 24 03:45:02at 
java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:1975)
2022-08-24T03:45:02.5933293Z Aug 24 03:45:02at 
org.apache.flink.util.concurrent.FutureUtils.doForward(FutureUtils.java:1277)
2022-08-24T03:45:02.5934708Z Aug 24 03:45:02at 
org.apache.flink.runtime.concurrent.akka.ClassLoadingUtils.lambda$null$1(ClassLoadingUtils.java:93)
2022-08-24T03:45:02.5936228Z Aug 24 03:45:02at 
org.apache.flink.runtime.concurrent.akka.ClassLoadingUtils.runWithContextClassLoader(ClassLoadingUtils.java:68)
2022-08-24T03:45:02.5937998Z Aug 24 03:45:02at 
org.apache.flink.runtime.concurrent.akka.ClassLoadingUtils.lambda$guardCompletionWithContextClassLoader$2(ClassLoadingUtils.java:92)
2022-08-24T03:45:02.5939627Z Aug 24 03:45:02at 
java.util.concurrent.CompletableFuture.uniWhenComplete(CompletableFuture.java:774)
2022-08-24T03:45:02.5941051Z Aug 24 03:45:02at 
java.util.concurrent.CompletableFuture$UniWhenComplete.tryFire(CompletableFuture.java:750)
2022-08-24T03:45:02.5942650Z Aug 24 03:45:02at 
java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:488)
2022-08-24T03:45:02.5944203Z Aug 24 03:45:02at 
java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:1975)
2022-08-24T03:45:02.5945740Z Aug 24 03:45:02at 
org.apache.flink.runtime.concurrent.akka.AkkaFutureUtils$1.onComplete(AkkaFutureUtils.java:47)
2022-08-24T03:45:02.5947020Z Aug 24 03:45:02at 
akka.dispatch.OnComplete.internal(Future.scala:300)
2022-08-24T03:45:02.5948130Z Aug 24 03:45:02at 
akka.dispatch.OnComplete.internal(Future.scala:297)
2022-08-24T03:45:02.5949255Z Aug 24 03:45:02at 
akka.dispatch.japi$CallbackBridge.apply(Future.scala:224)
2022-08-24T03:45:02.5950405Z Aug 24 03:45:02at 
akka.dispatch.japi$CallbackBridge.apply(Future.scala:221)
2022-08-24T03:45:02.5951638Z Aug 24 03:45:02at 
scala.concurrent.impl.CallbackRunnable.run(Promise.scala:60)
2022-08-24T03:45:02.5953564Z Aug 24 03:45:02at 
org.apache.flink.runtime.concurrent.akka.AkkaFutureUtils$DirectExecutionContext.execute(AkkaFutureUtils.java:65)
2022-08-24T03:45:02.5955214Z Aug 24 03:45:02at 
scala.concurrent.impl.CallbackRunnable.executeWithValue(Promise.scala:68)
2022-08-24T03:45:02.5956587Z Aug 24 03:45:02at 
scala.concurrent.impl.Promise$DefaultPromise.$anonfun$tryComplete$1(Promise.scala:284)
2022-08-24T03:45:02.5958037Z Aug 24 03:45:02at 
scala.concurrent.impl.Promise$DefaultPromise.$anonfun$tryComplete$1$adapted(Promise.scala:284)
2022-08-24T03:45:02.5959448Z Aug 24 03:45:02at 
scala.concurrent.impl.Promise$DefaultPromise.tryComplete(Promise.scala:284)
2022-08-24T03:45:02.5960679Z Aug 24 03:45:02at 
akka.pattern.PromiseActorRef.$bang(AskSupport.scala:621)
2022-08-24T03:45:02.5962183Z Aug 24 03:45:02at 
akka.pattern.PipeToSupport$PipeableFuture$$anonfun$pipeTo$1.applyOrElse(PipeToSupport.scala:24)
2022-08-24T03:45:02.5963694Z Aug 24 03:45:02

[jira] [Created] (FLINK-29092) HadoopPathBasedPartFileWriterTest.testWriteFile failed with AssertionError

[Xingbo Huang (Jira)]

Xingbo Huang created FLINK-29092:


 Summary: HadoopPathBasedPartFileWriterTest.testWriteFile failed 
with AssertionError
 Key: FLINK-29092
 URL: https://issues.apache.org/jira/browse/FLINK-29092
 Project: Flink
  Issue Type: Bug
  Components: Formats (JSON, Avro, Parquet, ORC, SequenceFile)
Affects Versions: 1.16.0
Reporter: Xingbo Huang
 Fix For: 1.16.0


{code:java}
2022-08-24T02:00:01.1670618Z Aug 24 02:00:01 [ERROR] 
org.apache.flink.formats.hadoop.bulk.HadoopPathBasedPartFileWriterTest.testWriteFile
  Time elapsed: 2.311 s  <<< FAILURE!
2022-08-24T02:00:01.1671250Z Aug 24 02:00:01 java.lang.AssertionError: 
2022-08-24T02:00:01.1671626Z Aug 24 02:00:01 
2022-08-24T02:00:01.1672001Z Aug 24 02:00:01 Expected size: 1 but was: 2 in:
2022-08-24T02:00:01.1673656Z Aug 24 02:00:01 
[DeprecatedRawLocalFileStatus{path=file:/tmp/junit3893779198554813459/junit1595046776902782406/2022-08-24--02;
 isDirectory=true; modification_time=166130640; access_time=1661306400396; 
owner=; group=; permission=rwxrwxrwx; isSymlink=false; hasAcl=false; 
isEncrypted=false; isErasureCoded=false},
2022-08-24T02:00:01.1676131Z Aug 24 02:00:01 
DeprecatedRawLocalFileStatus{path=file:/tmp/junit3893779198554813459/junit1595046776902782406/2022-08-24--01;
 isDirectory=true; modification_time=166130640; access_time=1661306400326; 
owner=; group=; permission=rwxrwxrwx; isSymlink=false; hasAcl=false; 
isEncrypted=false; isErasureCoded=false}]
2022-08-24T02:00:01.1677339Z Aug 24 02:00:01at 
org.apache.flink.formats.hadoop.bulk.HadoopPathBasedPartFileWriterTest.validateResult(HadoopPathBasedPartFileWriterTest.java:107)
2022-08-24T02:00:01.1678274Z Aug 24 02:00:01at 
org.apache.flink.formats.hadoop.bulk.HadoopPathBasedPartFileWriterTest.testWriteFile(HadoopPathBasedPartFileWriterTest.java:97)
2022-08-24T02:00:01.1679017Z Aug 24 02:00:01at 
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
2022-08-24T02:00:01.1679666Z Aug 24 02:00:01at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
2022-08-24T02:00:01.1680369Z Aug 24 02:00:01at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
2022-08-24T02:00:01.1681019Z Aug 24 02:00:01at 
java.lang.reflect.Method.invoke(Method.java:498)
2022-08-24T02:00:01.1681666Z Aug 24 02:00:01at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:59)
2022-08-24T02:00:01.1682385Z Aug 24 02:00:01at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
2022-08-24T02:00:01.1683094Z Aug 24 02:00:01at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:56)
2022-08-24T02:00:01.1683965Z Aug 24 02:00:01at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
2022-08-24T02:00:01.1684713Z Aug 24 02:00:01at 
org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
2022-08-24T02:00:01.1685956Z Aug 24 02:00:01at 
org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:299)
2022-08-24T02:00:01.1687185Z Aug 24 02:00:01at 
org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:293)
2022-08-24T02:00:01.1688347Z Aug 24 02:00:01at 
java.util.concurrent.FutureTask.run(FutureTask.java:266)
2022-08-24T02:00:01.1689324Z Aug 24 02:00:01at 
java.lang.Thread.run(Thread.java:748)
2022-08-24T02:00:01.1690062Z Aug 24 02:00:01 
2022-08-24T02:00:03.4727706Z Aug 24 02:00:03 Formatting using clusterid: 
testClusterID
2022-08-24T02:00:07.9860626Z Aug 24 02:00:07 [INFO] Tests run: 12, Failures: 0, 
Errors: 0, Skipped: 0, Time elapsed: 13.712 s - in 
org.apache.flink.formats.hadoop.bulk.committer.HadoopRenameCommitterHDFSTest
2022-08-24T02:00:08.4139747Z Aug 24 02:00:08 [INFO] 
2022-08-24T02:00:08.4140678Z Aug 24 02:00:08 [INFO] Results:
2022-08-24T02:00:08.4141326Z Aug 24 02:00:08 [INFO] 
2022-08-24T02:00:08.4142008Z Aug 24 02:00:08 [ERROR] Failures: 
2022-08-24T02:00:08.4144242Z Aug 24 02:00:08 [ERROR]   
HadoopPathBasedPartFileWriterTest.testWriteFile:97->validateResult:107 
2022-08-24T02:00:08.4145317Z Aug 24 02:00:08 Expected size: 1 but was: 2 in:
2022-08-24T02:00:08.4147711Z Aug 24 02:00:08 
[DeprecatedRawLocalFileStatus{path=file:/tmp/junit3893779198554813459/junit1595046776902782406/2022-08-24--02;
 isDirectory=true; modification_time=166130640; access_time=1661306400396; 
owner=; group=; permission=rwxrwxrwx; isSymlink=false; hasAcl=false; 
isEncrypted=false; isErasureCoded=false},
2022-08-24T02:00:08.4150885Z Aug 24 02:00:08 
DeprecatedRawLocalFileStatus{path=file:/tmp/junit3893779198554813459/junit1595046776902782406/2022-08-24--01;
 isDirectory=true; modification_time=166130640; access_time=1661306400326; 
owner=; group=

[SUMMARY] Flink 1.16 release sync of 2022-08-23

[Xingbo Huang]

I would like to give you a brief update of the Flink 1.16 release sync
meating of 2022-08-23.

*Since the feature freeze(9th of August 2022, end of business CEST), we
have started release-testing[1] in the last two weeks. Only two tickets
have been completed so far. We hope that the testers of the release-testing
JIRAs can update the progress in time. Our planned release time is the end
of September 2022. Based on this, we plan to finish the release-testing
work by the end of August.*

*Currently, there are still some critical/blocker stability tickets[2] that
need to be resolved. We will cut 1.16 branch once our CI is stable and
release-testing work has been finished.*

For more information about Flink release 1.16, you can refer to
https://cwiki.apache.org/confluence/display/FLINK/1.16+Release

The next Flink release sync will be on Tuesday the 30th of August at 9am
CEST/ 3pm China Standard Time / 7am UTC. The link could be found on the
following page
https://cwiki.apache.org/confluence/display/FLINK/1.16+Release#id-1.16Release-Syncmeeting
.

On behalf of all the release managers,

best regards,
Xingbo

[1] https://issues.apache.org/jira/browse/FLINK-28896
[2]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLINK%20AND%20issuetype%20%3D%20Bug%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20priority%20in%20(Blocker%2C%20Critical)%20AND%20fixVersion%20%3D%201.16.0%20ORDER%20BY%20summary%20ASC%2C%20priority%20DESC

Re: [VOTE] Release 1.15.2, release candidate #2

[Xingbo Huang]

+1 (non-binding)

- verify signatures and checksums
- no binaries found in source archive
- reviewed the release note blog
- verify python wheel package contents
- pip install apache-flink-libraries and apache-flink wheel packages
- run the examples from Python Table API tutorial

Best,
Xingbo

Chesnay Schepler  于2022年8月19日周五 15:51写道：

> +1 (binding)
>
> - signatures OK
> - all required artifacts on dist.apache.org
> - maven artifacts appear complete
> - tag exists
> - PR OK
> - no PaxHeader directories
> - no excessive files in the distribution
>
> On 17/08/2022 19:52, Danny Cranmer wrote:
> > Hi everyone,
> >
> > Please review and vote on the release candidate #2 for the version
> 1.15.2,
> > 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],
> > - the official Apache source release and binary convenience releases
> to
> > be deployed to dist.apache.org [2], which are signed with the key
> with
> > fingerprint 125FD8DB [3],
> > - all artifacts to be deployed to the Maven Central Repository [4],
> > - source code tag "release-1.15.2-rc2" [5],
> > - website pull request listing the new release and adding
> announcement
> > blog post [6].
> >
> >
> > The vote will be open for at least 72 hours. It is adopted by majority
> > approval, with at least 3 PMC affirmative votes.
> >
> > 1.15.2-RC1 was rejected for 2x issues:
> >
> > 1. Dist/src archives contained PaxHeader files when decompressing on
> > Windows. Root cause was tar default archive format on Mac, fixed by
> using
> > gnu-tar. I will follow up to update the release process to avoid
> this issue
> > in the future.
> > 2. Dist/src archives contained additional files. I had some locally
> > gitignored files that ended up in the archive. New build used a
> fresh clone
> > of Flink and I compared the archive contents of 1.15.1 with 1.15.2.
> >
> >
> > Thanks,
> > Danny Cranmer
> >
> > [1]
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12351829
> > [2] https://dist.apache.org/repos/dist/dev/flink/flink-1.15.2-rc2/
> > [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> > [4]
> https://repository.apache.org/content/repositories/orgapacheflink-1524
> > [5] https://github.com/apache/flink/tree/release-1.15.2-rc2
> > [6] https://github.com/apache/flink-web/pull/566
> >
>
>

Re: [ANNOUNCE] New Apache Flink Committer - Lijie Wang

[Xingbo Huang]

Congrats, Lijie

Best,
Xingbo

Lincoln Lee  于2022年8月18日周四 11:01写道：

> Congratulations, Lijie!
>
> Best,
> Lincoln Lee
>
>
> Benchao Li  于2022年8月18日周四 10:51写道：
>
> > Congratulations Lijie!
> >
> > yanfei lei  于2022年8月18日周四 10:44写道：
> >
> > > Congratulations, Lijie!
> > >
> > > Best,
> > > Yanfei
> > >
> > > JunRui Lee  于2022年8月18日周四 10:35写道：
> > >
> > > > Congratulations, Lijie!
> > > >
> > > > Best,
> > > > JunRui
> > > >
> > > > Timo Walther  于2022年8月17日周三 19:30写道：
> > > >
> > > > > Congratulations and welcome to the committer team :-)
> > > > >
> > > > > Regards,
> > > > > Timo
> > > > >
> > > > >
> > > > > On 17.08.22 12:50, Yuxin Tan wrote:
> > > > > > Congratulations, Lijie!
> > > > > >
> > > > > > Best,
> > > > > > Yuxin
> > > > > >
> > > > > >
> > > > > > Guowei Ma  于2022年8月17日周三 18:42写道：
> > > > > >
> > > > > >> Congratulations, Lijie. Welcome on board~!
> > > > > >> Best,
> > > > > >> Guowei
> > > > > >>
> > > > > >>
> > > > > >> On Wed, Aug 17, 2022 at 6:25 PM Zhu Zhu 
> wrote:
> > > > > >>
> > > > > >>> Hi everyone,
> > > > > >>>
> > > > > >>> On behalf of the PMC, I'm very happy to announce Lijie Wang as
> > > > > >>> a new Flink committer.
> > > > > >>>
> > > > > >>> Lijie has been contributing to Flink project for more than 2
> > years.
> > > > > >>> He mainly works on the runtime/coordination part, doing feature
> > > > > >>> development, problem debugging and code reviews. He has also
> > > > > >>> driven the work of FLIP-187(Adaptive Batch Scheduler) and
> > > > > >>> FLIP-224(Blocklist for Speculative Execution), which are
> > important
> > > > > >>> to run batch jobs.
> > > > > >>>
> > > > > >>> Please join me in congratulating Lijie for becoming a Flink
> > > > committer!
> > > > > >>>
> > > > > >>> Cheers,
> > > > > >>> Zhu
> > > > > >>>
> > > > > >>
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> >
> >
> > --
> >
> > Best,
> > Benchao Li
> >
>

[SUMMARY] Flink 1.16 release sync of 2022-08-16

[Xingbo Huang]

Hi everyone,

I would like to give you a brief update of the Flink 1.16 release sync
meating of 2022-08-16.

*In the last Wednesday(9th of August 2022, end of business CEST), we
announced the feature freeze. And after that, we have started release
testing work. I have created an umbrella release testing JIRA[1] and many
child JIRAs about new features have been created. If your added new
features need cross-team testing, you can also create a child JIRA. We will
help find volunteers to test the related feature. At meantime, welcome to
volunteer to help test our new features in release 1.16. Your help is much
appreciated.*

*Currently, there are still some critical/blocker stability tickets[2] that
need to be resolved. We will cut 1.16 branch once our CI is stable and
release-testing work has been finished.*

For more information about Flink release 1.16, you can refer to
https://cwiki.apache.org/confluence/display/FLINK/1.16+Release

The next Flink release sync will be on Tuesday the 23rd of August at 9am
CEST/ 3pm China Standard Time / 7am UTC. The link could be found on the
following page
https://cwiki.apache.org/confluence/display/FLINK/1.16+Release#id-1.16Release-Syncmeeting
.

On behalf of all the release managers,

best regards,
Xingbo

[1] https://issues.apache.org/jira/browse/FLINK-28896
[2]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLINK%20AND%20issuetype%20%3D%20Bug%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20priority%20in%20(Blocker%2C%20Critical)%20AND%20fixVersion%20%3D%201.16.0%20ORDER%20BY%20summary%20ASC%2C%20priority%20DESC

Re: [DISCUSS] Releasing Flink 1.15.2

[Xingbo Huang]

Hi Danny,

Thanks for driving the release. +1 for the 1.15.2 release.

Best,
Xingbo

Chesnay Schepler  于2022年8月11日周四 20:06写道：

> I think that's a good idea; a user in the Flink slack was asking for it
> just yesterday.
>
> About FLINK-28861, let's wait a day or something because there should be
> PR very soon.
>
> It's perfectly fine for you to be the release manager; I can help you
> out with things with that require PMC permissions.
>
> On 11/08/2022 12:39, Danny Cranmer wrote:
> > Hello all,
> >
> > I would like to start discussing the release of Flink 1.15.2. Flink
> 1.15.1
> > was released on 6th July [1] and we have resolved 31 issues since then
> [2].
> > During the Flink 1.15.1 vote [3] we identified one blocker [4] and one
> > critical issue [5] that should be fixed soon after. We also have 3 other
> > non-test related critical fixes merged into 1.15.2.
> >
> > There is 1 blocker in 1.15.2 not yet resolved that we could consider
> > waiting for, "Cannot resume from savepoint when using fromChangelogStream
> > in upsert mode" [6]. There have been discussions on this issue and it
> looks
> > like Timo will be working on it, however there is no PR available yet.
> >
> > I'd like to advocate this release and in doing so nominate myself to be
> the
> > release manager. I'm conscious that I have not performed this duty
> before,
> > so alternatively am happy to shadow this process if I can find a willing
> > volunteer to cover it on this occasion.
> >
> > [1] https://flink.apache.org/news/2022/07/06/release-1.15.1.html
> > [2]
> >
> https://issues.apache.org/jira/browse/FLINK-28322?jql=project%20%3D%20FLINK%20AND%20fixVersion%20%3D%201.15.2%20AND%20status%20in%20(resolved%2C%20closed)%20order%20by%20priority%20desc
> > [3] https://lists.apache.org/thread/t27qc36g141kzk8d83jytkdshfpdj0xl
> > [4] https://issues.apache.org/jira/browse/FLINK-28322
> > [5] https://issues.apache.org/jira/browse/FLINK-23528
> > [6] https://issues.apache.org/jira/browse/FLINK-28861
> >
> > Thanks,
> > Danny Cranmer
> >
>
>

[jira] [Created] (FLINK-28901) CassandraSinkBaseTest.testTimeoutExceptionOnInvoke failed with TestTimedOutException

[Xingbo Huang (Jira)]

Xingbo Huang created FLINK-28901:


 Summary: CassandraSinkBaseTest.testTimeoutExceptionOnInvoke failed 
with TestTimedOutException
 Key: FLINK-28901
 URL: https://issues.apache.org/jira/browse/FLINK-28901
 Project: Flink
  Issue Type: Bug
  Components: Connectors / Cassandra
Affects Versions: 1.16.0
Reporter: Xingbo Huang
 Fix For: 1.16.0



{code:java}
2022-08-10T03:39:22.6587394Z Aug 10 03:39:22 [ERROR] 
org.apache.flink.streaming.connectors.cassandra.CassandraSinkBaseTest.testTimeoutExceptionOnInvoke
  Time elapsed: 5.113 s  <<< ERROR!
2022-08-10T03:39:22.6588579Z Aug 10 03:39:22 
org.junit.runners.model.TestTimedOutException: test timed out after 5000 
milliseconds
2022-08-10T03:39:22.6589463Z Aug 10 03:39:22at 
java.util.zip.ZipFile.read(Native Method)
2022-08-10T03:39:22.6590286Z Aug 10 03:39:22at 
java.util.zip.ZipFile.access$1400(ZipFile.java:60)
2022-08-10T03:39:22.6591287Z Aug 10 03:39:22at 
java.util.zip.ZipFile$ZipFileInputStream.read(ZipFile.java:734)
2022-08-10T03:39:22.6592323Z Aug 10 03:39:22at 
java.util.zip.ZipFile$ZipFileInflaterInputStream.fill(ZipFile.java:434)
2022-08-10T03:39:22.6593673Z Aug 10 03:39:22at 
java.util.zip.InflaterInputStream.read(InflaterInputStream.java:158)
2022-08-10T03:39:22.6594638Z Aug 10 03:39:22at 
sun.misc.Resource.getBytes(Resource.java:124)
2022-08-10T03:39:22.6595535Z Aug 10 03:39:22at 
java.net.URLClassLoader.defineClass(URLClassLoader.java:463)
2022-08-10T03:39:22.6596506Z Aug 10 03:39:22at 
java.net.URLClassLoader.access$100(URLClassLoader.java:74)
2022-08-10T03:39:22.6597477Z Aug 10 03:39:22at 
java.net.URLClassLoader$1.run(URLClassLoader.java:369)
2022-08-10T03:39:22.6598393Z Aug 10 03:39:22at 
java.net.URLClassLoader$1.run(URLClassLoader.java:363)
2022-08-10T03:39:22.6599286Z Aug 10 03:39:22at 
java.security.AccessController.doPrivileged(Native Method)
2022-08-10T03:39:22.6600209Z Aug 10 03:39:22at 
java.net.URLClassLoader.findClass(URLClassLoader.java:362)
2022-08-10T03:39:22.6601141Z Aug 10 03:39:22at 
java.lang.ClassLoader.loadClass(ClassLoader.java:418)
2022-08-10T03:39:22.6602070Z Aug 10 03:39:22at 
sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
2022-08-10T03:39:22.6603090Z Aug 10 03:39:22at 
java.lang.ClassLoader.loadClass(ClassLoader.java:351)
2022-08-10T03:39:22.6604199Z Aug 10 03:39:22at 
net.bytebuddy.NamingStrategy$SuffixingRandom.(NamingStrategy.java:153)
2022-08-10T03:39:22.6605188Z Aug 10 03:39:22at 
net.bytebuddy.ByteBuddy.(ByteBuddy.java:196)
2022-08-10T03:39:22.6606063Z Aug 10 03:39:22at 
net.bytebuddy.ByteBuddy.(ByteBuddy.java:187)
2022-08-10T03:39:22.6607141Z Aug 10 03:39:22at 
org.mockito.internal.creation.bytebuddy.InlineBytecodeGenerator.(InlineBytecodeGenerator.java:81)
2022-08-10T03:39:22.6608423Z Aug 10 03:39:22at 
org.mockito.internal.creation.bytebuddy.InlineByteBuddyMockMaker.(InlineByteBuddyMockMaker.java:224)
2022-08-10T03:39:22.6609844Z Aug 10 03:39:22at 
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
2022-08-10T03:39:22.6610990Z Aug 10 03:39:22at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
2022-08-10T03:39:22.6612246Z Aug 10 03:39:22at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
2022-08-10T03:39:22.6613551Z Aug 10 03:39:22at 
java.lang.reflect.Constructor.newInstance(Constructor.java:423)
2022-08-10T03:39:22.6614482Z Aug 10 03:39:22at 
java.lang.Class.newInstance(Class.java:442)
2022-08-10T03:39:22.6615527Z Aug 10 03:39:22at 
org.mockito.internal.configuration.plugins.PluginInitializer.loadImpl(PluginInitializer.java:50)
2022-08-10T03:39:22.6616718Z Aug 10 03:39:22at 
org.mockito.internal.configuration.plugins.PluginLoader.loadPlugin(PluginLoader.java:63)
2022-08-10T03:39:22.6617900Z Aug 10 03:39:22at 
org.mockito.internal.configuration.plugins.PluginLoader.loadPlugin(PluginLoader.java:48)
2022-08-10T03:39:22.6619079Z Aug 10 03:39:22at 
org.mockito.internal.configuration.plugins.PluginRegistry.(PluginRegistry.java:23)
2022-08-10T03:39:22.6620206Z Aug 10 03:39:22at 
org.mockito.internal.configuration.plugins.Plugins.(Plugins.java:19)
2022-08-10T03:39:22.6621435Z Aug 10 03:39:22at 
org.mockito.internal.util.MockUtil.(MockUtil.java:24)
2022-08-10T03:39:22.6622523Z Aug 10 03:39:22at 
org.mockito.internal.util.MockCreationValidator.validateType(MockCreationValidator.java:22)
2022-08-10T03:39:22.6623890Z Aug 10 03:39:22at 
org.mockito.internal.creation.MockSettingsImpl.validatedSettings(MockSettingsImpl.java:250)
2022-08-10T03:39:22.6625051Z Aug 10 03:39:22at 
org.mockito.internal.creation.MockSettingsImpl.build(MockSettingsImpl.java:232)
2022-08-10T03:39:22.6626085Z Aug 10

[jira] [Created] (FLINK-28900) RecreateOnResetOperatorCoordinatorTest compile failed in jdk11

[Xingbo Huang (Jira)]

Xingbo Huang created FLINK-28900:


 Summary: RecreateOnResetOperatorCoordinatorTest compile failed in 
jdk11
 Key: FLINK-28900
 URL: https://issues.apache.org/jira/browse/FLINK-28900
 Project: Flink
  Issue Type: Bug
  Components: Runtime / Coordination
Affects Versions: 1.16.0
Reporter: Xingbo Huang
 Fix For: 1.16.0



{code:java}
2022-08-10T00:19:25.3221073Z [ERROR] COMPILATION ERROR : 
2022-08-10T00:19:25.3221634Z [INFO] 
-
2022-08-10T00:19:25.3222878Z [ERROR] 
/__w/1/s/flink-runtime/src/test/java/org/apache/flink/runtime/operators/coordination/RecreateOnResetOperatorCoordinatorTest.java:[241,58]
 method containsExactly in class 
org.assertj.core.api.AbstractIterableAssert 
cannot be applied to given types;
2022-08-10T00:19:25.3223786Z   required: capture#1 of ? extends 
java.lang.Integer[]
2022-08-10T00:19:25.3224245Z   found: int
2022-08-10T00:19:25.3224684Z   reason: varargs mismatch; int cannot be 
converted to capture#1 of ? extends java.lang.Integer
2022-08-10T00:19:25.3225128Z [INFO] 1 error
{code}
https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=39795=logs=946871de-358d-5815-3994-8175615bc253=e0240c62-4570-5d1c-51af-dd63d2093da1



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (FLINK-28898) ChangelogRecoverySwitchStateBackendITCase.testSwitchFromEnablingToDisablingWithRescalingOut failed

[Xingbo Huang (Jira)]

Xingbo Huang created FLINK-28898:


 Summary: 
ChangelogRecoverySwitchStateBackendITCase.testSwitchFromEnablingToDisablingWithRescalingOut
 failed
 Key: FLINK-28898
 URL: https://issues.apache.org/jira/browse/FLINK-28898
 Project: Flink
  Issue Type: Bug
  Components: Runtime / Checkpointing, Runtime / State Backends
Affects Versions: 1.16.0
Reporter: Xingbo Huang
 Fix For: 1.16.0


{code:java}
2022-08-10T02:48:19.5711924Z Aug 10 02:48:19 [ERROR] 
ChangelogRecoverySwitchStateBackendITCase.testSwitchFromEnablingToDisablingWithRescalingOut
  Time elapsed: 6.064 s  <<< ERROR!
2022-08-10T02:48:19.5712815Z Aug 10 02:48:19 
org.apache.flink.runtime.JobException: Recovery is suppressed by 
FixedDelayRestartBackoffTimeStrategy(maxNumberRestartAttempts=0, 
backoffTimeMS=0)
2022-08-10T02:48:19.5714530Z Aug 10 02:48:19at 
org.apache.flink.runtime.executiongraph.failover.flip1.ExecutionFailureHandler.handleFailure(ExecutionFailureHandler.java:139)
2022-08-10T02:48:19.5716211Z Aug 10 02:48:19at 
org.apache.flink.runtime.executiongraph.failover.flip1.ExecutionFailureHandler.getFailureHandlingResult(ExecutionFailureHandler.java:83)
2022-08-10T02:48:19.5717627Z Aug 10 02:48:19at 
org.apache.flink.runtime.scheduler.DefaultScheduler.recordTaskFailure(DefaultScheduler.java:256)
2022-08-10T02:48:19.5718885Z Aug 10 02:48:19at 
org.apache.flink.runtime.scheduler.DefaultScheduler.handleTaskFailure(DefaultScheduler.java:247)
2022-08-10T02:48:19.5720430Z Aug 10 02:48:19at 
org.apache.flink.runtime.scheduler.DefaultScheduler.onTaskFailed(DefaultScheduler.java:240)
2022-08-10T02:48:19.5721733Z Aug 10 02:48:19at 
org.apache.flink.runtime.scheduler.SchedulerBase.onTaskExecutionStateUpdate(SchedulerBase.java:738)
2022-08-10T02:48:19.5722680Z Aug 10 02:48:19at 
org.apache.flink.runtime.scheduler.SchedulerBase.updateTaskExecutionState(SchedulerBase.java:715)
2022-08-10T02:48:19.5723612Z Aug 10 02:48:19at 
org.apache.flink.runtime.scheduler.SchedulerNG.updateTaskExecutionState(SchedulerNG.java:78)
2022-08-10T02:48:19.5724389Z Aug 10 02:48:19at 
org.apache.flink.runtime.jobmaster.JobMaster.updateTaskExecutionState(JobMaster.java:477)
2022-08-10T02:48:19.5725046Z Aug 10 02:48:19at 
sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source)
2022-08-10T02:48:19.5725708Z Aug 10 02:48:19at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
2022-08-10T02:48:19.5726374Z Aug 10 02:48:19at 
java.lang.reflect.Method.invoke(Method.java:498)
2022-08-10T02:48:19.5727065Z Aug 10 02:48:19at 
org.apache.flink.runtime.rpc.akka.AkkaRpcActor.lambda$handleRpcInvocation$1(AkkaRpcActor.java:309)
2022-08-10T02:48:19.5727932Z Aug 10 02:48:19at 
org.apache.flink.runtime.concurrent.akka.ClassLoadingUtils.runWithContextClassLoader(ClassLoadingUtils.java:83)
2022-08-10T02:48:19.5729087Z Aug 10 02:48:19at 
org.apache.flink.runtime.rpc.akka.AkkaRpcActor.handleRpcInvocation(AkkaRpcActor.java:307)
2022-08-10T02:48:19.5730134Z Aug 10 02:48:19at 
org.apache.flink.runtime.rpc.akka.AkkaRpcActor.handleRpcMessage(AkkaRpcActor.java:222)
2022-08-10T02:48:19.5731536Z Aug 10 02:48:19at 
org.apache.flink.runtime.rpc.akka.FencedAkkaRpcActor.handleRpcMessage(FencedAkkaRpcActor.java:84)
2022-08-10T02:48:19.5732549Z Aug 10 02:48:19at 
org.apache.flink.runtime.rpc.akka.AkkaRpcActor.handleMessage(AkkaRpcActor.java:168)
2022-08-10T02:48:19.5735018Z Aug 10 02:48:19at 
akka.japi.pf.UnitCaseStatement.apply(CaseStatements.scala:24)
2022-08-10T02:48:19.5735821Z Aug 10 02:48:19at 
akka.japi.pf.UnitCaseStatement.apply(CaseStatements.scala:20)
2022-08-10T02:48:19.5736465Z Aug 10 02:48:19at 
scala.PartialFunction.applyOrElse(PartialFunction.scala:123)
2022-08-10T02:48:19.5737234Z Aug 10 02:48:19at 
scala.PartialFunction.applyOrElse$(PartialFunction.scala:122)
2022-08-10T02:48:19.5737895Z Aug 10 02:48:19at 
akka.japi.pf.UnitCaseStatement.applyOrElse(CaseStatements.scala:20)
2022-08-10T02:48:19.5738574Z Aug 10 02:48:19at 
scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:171)
2022-08-10T02:48:19.5739276Z Aug 10 02:48:19at 
scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:172)
2022-08-10T02:48:19.5740315Z Aug 10 02:48:19at 
scala.PartialFunction$OrElse.applyOrElse(PartialFunction.scala:172)
2022-08-10T02:48:19.5741211Z Aug 10 02:48:19at 
akka.actor.Actor.aroundReceive(Actor.scala:537)
2022-08-10T02:48:19.5741878Z Aug 10 02:48:19at 
akka.actor.Actor.aroundReceive$(Actor.scala:535)
2022-08-10T02:48:19.5742497Z Aug 10 02:48:19at 
akka.actor.AbstractActor.aroundReceive(AbstractActor.scala:220)
2022-08-10T02:48:19.5743242Z Aug 10 02:48:19at 
akka.actor.ActorCell.receiveMessage(ActorCell.scala:580)
2022-08-10T02:48:19.5743977Z Aug 10 02:48:19at 
akka.actor.ActorCe

Re: [DISCUSS] Bump Kafka to 3.2.1 for 1.16.0

[Xingbo Huang]

I'm not sure if this kafka upgrade will bring other unknown problems, but
if this upgrade can help us solve known critical bugs, the sooner the
upgrade, the better. Before cutting release-1.16 branch, we will still have
enough time to test the impact.

So I'm +1 for including this fix in 1.16.0.

Best,
Xingbo

Mason Chen  于2022年8月10日周三 07:20写道：

> +1
>
> We don't have a reproducible test in Flink CI to tell if the issue is
> definitely solved. However, bumping the version doesn't make matters worse
> then the current state.
>
> Best,
> Mason
>
> On Tue, Aug 9, 2022 at 10:56 AM David Anderson 
> wrote:
>
> > I'm in favor of adopting this fix in 1.16.0.
> >
> > +1
> >
> > On Tue, Aug 9, 2022 at 7:13 AM tison  wrote:
> >
> > > +1
> > >
> > > This looks reasonable.
> > >
> > > Best,
> > > tison.
> > >
> > >
> > > Thomas Weise  于2022年8月9日周二 21:33写道：
> > >
> > > > +1 for bumping the Kafka dependency.
> > > >
> > > > Flink X.Y.0 releases require thorough testing, so considering the
> > > severity
> > > > of the problem this is still good timing, even that close to the
> first
> > > RC.
> > > >
> > > > Thanks for bringing this up.
> > > >
> > > > Thomas
> > > >
> > > > On Tue, Aug 9, 2022 at 7:51 AM Chesnay Schepler 
> > > > wrote:
> > > >
> > > > > Hello,
> > > > >
> > > > > The Kafka upgrade in 1.15.0 resulted in a regression
> > > > > (https://issues.apache.org/jira/browse/FLINK-28060) where offsets
> > are
> > > > > not committed to Kafka, impeding monitoring and the starting
> offsets
> > > > > functionality of the connector.
> > > > >
> > > > > This has been fixed a about a week ago in Kafka 3.2.1.
> > > > >
> > > > > The question is whether we want to upgrade Kafka so close to the
> > > feature
> > > > > freeze. I'm usually not a friend of doing that in general, but in
> > this
> > > > > case there is a specific issue we'd like to get fixed and we still
> > have
> > > > > the entire duration of the feature freeze to observe the behavior.
> > > > >
> > > > > I'd like to know what you think about this.
> > > > >
> > > > > For reference, our current Kafka version is 3.1.1, and our CI is
> > > passing
> > > > > with 3.2.1.
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>

[SUMMARY] Flink 1.16 release sync of 2022-08-09

[Xingbo Huang]

Hi everyone,

I would like to give you a brief update of the Flink 1.16 release sync
meating of 2022-08-09.

* Currently, we have 40 features that have been completed for this release
and 6 features are still expected to make it (PS: Most of them are already
reviewed and are just waiting for the CI pass).

* We plan to announce feature freeze on 9th of August 2022, end of business
CEST. If you need an exception to this rule, please open a discussion on
dev@ list and reach out to us.

* Currently, we still have many new features that do not provide
corresponding documentation. Please complete them as soon as possible,
otherwise it will not be conducive to our cross-team testing.

* After feature freeze, we will start the work of preparing release notes
and testing.

* Some of our new features' umbrella JIRAs are only partially included in
1.16. For the child JIRAs that are not included in this release, we will
move them to a new umbrella, which is beneficial to view the status of the
feature.

* There are still some critical/blocker stability tickets[1] that need to
be resolved.

For more information about Flink release 1.16, you can refer to
https://cwiki.apache.org/confluence/display/FLINK/1.16+Release

The next Flink release sync will be on Tuesday the 16th of August at 9am
CEST/ 3pm China Standard Time / 7am UTC. The link could be found on the
following page
https://cwiki.apache.org/confluence/display/FLINK/1.16+Release#id-1.16Release-Syncmeeting
.

On behalf of all the release managers,

best regards,
Xingbo

[1]
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=561=planning=FLINK-28766=2540=100

Re: [SUMMARY] Flink 1.16 release sync of 2022-08-02

[Xingbo Huang]

Martijn has changed the previous meeting link in the 1.16 doc. I'll post
the summary of today's release sync later.

Chesnay Schepler  于2022年8月9日周二 15:40写道：

> The sync did happen; it was reachable under the same google meet link in
> the 1.16 doc as usual.
>
> On 09/08/2022 09:31, Robert Metzger wrote:
> > Thanks for the summary.
> >
> > I tried joining the sync today, but nobody joined. On the Flink Slack,
> > Martijn's status is set to vacation, so I guess the meeting didn't happen
> > today?
> >
> > It seems that the pulsar blocker (FLINK-27399) is still open, but the PR
> > seems to make progress.
> >
> > On Wed, Aug 3, 2022 at 6:46 AM Xingbo Huang  wrote:
> >
> >> Hi everyone,
> >>
> >> I would like to give you a brief update of the Flink 1.16 release sync
> >> meating of 2022-08-02.
> >>
> >> Currently, we have 19 features that have been completed for this release
> >> and 32 features are still expected to make it. We only have one week
> >> remaining until the feature freeze (at 2022-08-09), which means that we
> >> will start with the release testing and cut the release branch once the
> CI
> >> is stable[1].
> >>
> >> We currently have one blocker ticket[2] that is being worked on. Many
> >> thanks to these contributors and reviewers.
> >>
> >> Next, we also have some critical test stability tickets[2] that are not
> >> picked up. We need to guarantee the CI stable before the release branch
> >> cut. You can either directly assign it to yourself (don't forget to
> mark it
> >> as In Progress) or ping me (@Huang Xingbo) to get it assigned to you.
> Your
> >> help is much appreciated.
> >>
> >> For more information about Flink release 1.16, you can refer to
> >> https://cwiki.apache.org/confluence/display/FLINK/1.16+Release
> >>
> >> The next Flink release sync will be on Tuesday the 9th of August at 9am
> >> CEST/ 3pm China Standard Time / 7am UTC. The link can also be found on
> the
> >> first page.
> >>
> >> On behalf of all the release managers,
> >>
> >> best regards,
> >> Xingbo
> >>
> >> [1]
> >>
> >>
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=561=planning=FLINK-28766=2540=100
> >> [2]
> >>
> >>
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=561=planning=FLINK-27399=2539=100
> >> [3]
> >>
> >>
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=561=FLINK=planning=FLINK-28440=2540=2544=100
> >>
>
>

[jira] [Created] (FLINK-28788) Support SideOutput in Thread Mode

[Xingbo Huang (Jira)]

Xingbo Huang created FLINK-28788:


 Summary: Support SideOutput in Thread Mode
 Key: FLINK-28788
 URL: https://issues.apache.org/jira/browse/FLINK-28788
 Project: Flink
  Issue Type: New Feature
  Components: API / Python
Affects Versions: 1.16.0
Reporter: Xingbo Huang
Assignee: Xingbo Huang
 Fix For: 1.16.0






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[SUMMARY] Flink 1.16 release sync of 2022-08-02

[Xingbo Huang]

Hi everyone,

I would like to give you a brief update of the Flink 1.16 release sync
meating of 2022-08-02.

Currently, we have 19 features that have been completed for this release
and 32 features are still expected to make it. We only have one week
remaining until the feature freeze (at 2022-08-09), which means that we
will start with the release testing and cut the release branch once the CI
is stable[1].

We currently have one blocker ticket[2] that is being worked on. Many
thanks to these contributors and reviewers.

Next, we also have some critical test stability tickets[2] that are not
picked up. We need to guarantee the CI stable before the release branch
cut. You can either directly assign it to yourself (don't forget to mark it
as In Progress) or ping me (@Huang Xingbo) to get it assigned to you. Your
help is much appreciated.

For more information about Flink release 1.16, you can refer to
https://cwiki.apache.org/confluence/display/FLINK/1.16+Release

The next Flink release sync will be on Tuesday the 9th of August at 9am
CEST/ 3pm China Standard Time / 7am UTC. The link can also be found on the
first page.

On behalf of all the release managers,

best regards,
Xingbo

[1]
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=561=planning=FLINK-28766=2540=100
[2]
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=561=planning=FLINK-27399=2539=100
[3]
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=561=FLINK=planning=FLINK-28440=2540=2544=100

Re: I want to contribute to Apache Flink.

[Xingbo Huang]

Hi,

Thanks for reaching out. Please follow
https://flink.apache.org/contributing/contribute-code.html to start with
your contribution.
You don't need to be in any list to start your contribution.

Best,
Xingbo

黄如飞 <1369612...@qq.com.invalid> 于2022年7月28日周四 11:25写道：

> Hi Guys,
> I want to contribute to Apache Flink.
> Would you please give me the permission as a contributor?
> My JIRA username is Rufy666
>
>
>
>
> 黄如飞
> 1369612...@qq.com
>
>
>
> 

[SUMMARY] Flink 1.16 release sync of 2022-07-26

[Xingbo Huang]

Hi everyone,

I would like to give you a brief update of the Flink 1.16 release sync
meating of 2022-07-26.

Currently, we have 17 features that have been completed for this release
and 35 features are still expected to make it. We only have 2 weeks
remaining until the feature freeze (at 2022-08-09).

We currently have two blocker tickets that are being worked on. Many thanks
to these contributors and reviewers.

Next, we also have some critical test stability tickets[1] that are not
picked up. We need to guarantee the CI stable before the release branch
cut. You can either directly assign it to yourself (don't forget to mark it
as In Progress) or ping me (@Huang Xingbo) to get it assigned to you. Your
help is much appreciated.

For more information about Flink release 1.16, you can refer to
https://cwiki.apache.org/confluence/display/FLINK/1.16+Release

The next Flink release sync will be on Tuesday the 2nd of August at 9am
CEST/ 3pm China Standard Time / 7am UTC. The link can also be found on the
first page.

On behalf of all the release managers,

best regards,
Xingbo

[1]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLINK%20AND%20issuetype%20%3D%20Bug%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20priority%20in%20(Blocker%2C%20Critical)%20AND%20labels%20%3D%20test-stability%20AND%20assignee%20in%20(EMPTY)%20ORDER%20BY%20updated%20DESC%2C%20summary%20DESC

[SUMMARY] Flink 1.16 release sync of 2022-07-19

[Xingbo Huang]

Hi everyone,

I would like to give you a brief update of the Flink 1.16 release status
till 2022-07-19.

Currently, we have 12 features that have been completed for this release
and 41 features are still expected to make it. We only have 3 weeks
remaining until the feature freeze (at 2022-08-09).

We currently have one blocker ticket that is being worked on. Many thanks
to these contributors and reviewers.

Next, we also have some critical test stability tickets[1] that are not
picked up. We need to guarantee the CI stable before the release branch
cut. You can either directly assign it to yourself (don't forget to mark it
as In Progress) or ping me (@Huang Xingbo) to get it assigned to you. Your
help is much appreciated.

For more information about Flink release 1.16, you can refer to
https://cwiki.apache.org/confluence/display/FLINK/1.16+Release

The next Flink release sync will be on Tuesday the 26th of July at 9am
CEST/ 3pm China Standard Time / 7am UTC. The link can also be found on the
first page.

On behalf of all the release managers, best regards,

Xingbo

[1]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLINK%20AND%20issuetype%20%3D%20Bug%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20priority%20in%20(Blocker%2C%20Critical)%20AND%20labels%20%3D%20test-stability%20AND%20assignee%20in%20(EMPTY)%20ORDER%20BY%20updated%20DESC%2C%20summary%20DESC

Re: [DISCUSS] Creating benchmark channel in Apache Flink slack

[Xingbo Huang]

+1 for creating a public slack channel for benchmark. Like the build
channel, it will help us find potential problems before release.

Best,
Xingbo

Jing Ge  于2022年7月7日周四 22:41写道：

> +1 for moving to the public slack channel. Flink developers should pay more
> attention to the performance test.
>
> Best regards,
> Jing
>
> On Thu, Jul 7, 2022 at 2:02 PM Yuan Mei  wrote:
>
> > +1 for the proposal Anton, and thanks very much to move this effort
> > forward!
> >
> > In long term, I think it would be helpful to ask volunteers to help
> > watching-out the daily micro benchmark results.
> >
> > But let's make it more visible as the very first step!
> >
> > Best Regards,
> >
> > Yuan
> >
> > On Tue, Jul 5, 2022 at 10:18 PM Martijn Visser  >
> > wrote:
> >
> > > Hi Anton,
> > >
> > > I recalled that it was brought up before and it was indeed (when the
> > > announcement email was sent [1]).
> > >
> > > +1 for doing this.
> > >
> > > Best regards,
> > >
> > > Martijn
> > >
> > > [1] https://lists.apache.org/thread/kqjtrlnw33h1mybyx3gg4ff4390y5wbz
> > >
> > > Op di 5 jul. 2022 om 16:12 schreef Piotr Nowojski <
> pnowoj...@apache.org
> > >:
> > >
> > > > Hi Anton,
> > > >
> > > > Thanks for the proposal. +1 for this. The higher visibility in the
> > > > community of the benchmarks, benchmarking process and it's result the
> > > > better.
> > > >
> > > > Best,
> > > > Piotrek
> > > >
> > > > wt., 5 lip 2022 o 16:10 Anton Kalashnikov 
> > > napisał(a):
> > > >
> > > > > Hi everyone,
> > > > >
> > > > >
> > > > > As you know, we have Flink benchmarks[1], and all of these
> benchmarks
> > > > > constantly running several times per day. The result of this can be
> > > > > found in Codespeed panel[2].
> > > > >
> > > > > The problem is that only several people follow the result of these
> > > > > benchmarks since it is not possible to ask everybody constantly pay
> > > > > attention to this result page.
> > > > >
> > > > > The idea is to create `dev-benchmarks` channel(the name is
> > > discussable).
> > > > > Then we can create 'Slack app'[3] for benchmarks and send the
> result
> > of
> > > > > each benchmark's run to this channel.
> > > > >
> > > > > I think it should make benchmarks more visible to the community.
> > > > >
> > > > > We can discuss the information that should be sent but the main
> idea
> > is
> > > > > to follow all fails and regression of benchmarks.
> > > > >
> > > > > It also makes sense to mention that right now it is easy
> > > > > enough(especially after [4]) to configure our benchmarks in Jenkins
> > > > > since we have all scripts in the repository. So even in the case,
> we
> > > > > will lose our current server we can easily setup the new one.
> > > > >
> > > > >
> > > > > WDYT?
> > > > >
> > > > >
> > > > > [1] https://github.com/apache/flink-benchmarks
> > > > >
> > > > > [2] http://codespeed.dak8s.net:8000/changes/
> > > > >
> > > > > [3]
> > https://plugins.jenkins.io/slack/#plugin-content-creating-your-app
> > > > >
> > > > > [4] https://issues.apache.org/jira/browse/FLINK-28407
> > > > >
> > > > > --
> > > > >
> > > > > Best regards,
> > > > > Anton Kalashnikov
> > > > >
> > > > >
> > > >
> > >
> >
>

Re: [ANNOUNCE] Apache Flink 1.15.1 released

[Xingbo Huang]

Thanks a lot for being our release manager David and everyone who
contributed.

Best,
Xingbo

David Anderson  于2022年7月8日周五 06:18写道：

> The Apache Flink community is very happy to announce the release of Apache
> Flink 1.15.1, which is the first bugfix release for the Apache Flink 1.15
> series.
>
> Apache Flink® is an open-source stream processing framework for
> distributed, high-performing, always-available, and accurate data streaming
> applications.
>
> The release is available for download at:
> https://flink.apache.org/downloads.html
>
> Please check out the release blog post for an overview of the improvements
> for this bugfix release:
>
> https://flink.apache.org/news/2022/07/06/release-1.15.1.html
>
> The full release notes are available in Jira:
>
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12351546
>
> We would like to thank all contributors of the Apache Flink community who
> made this release possible!
>
> Regards,
> David Anderson
>

Re: [ACTION REQUESTED] Flink 1.16 Release Sync update

[Xingbo Huang]

Hi Martjin,

I have discussed offline with several contributors from China and found
that most of them thought it difficult to finish the on-going features by
25th July. As there is consensus[1][2] that the feature freeze will happen
by the end of July with potentially two weeks delay, do you think it makes
sense to postpone the feature freeze date a bit(maybe two weeks or so) as
there are still 44 planned tasks are on-going and only 8 of them are
finished[3]?

Regarding the release branch cut time, in previous releases, after feature
freeze, it usually waits about two weeks or so before cutting the release
branch. This could avoid pushing to two branches at the same time which may
happen more frequently than usual. Should we also follow that practice in
this release?

Best,
Xingbo

[1] https://lists.apache.org/thread/ghfb5xdjy7tv0zqlrxvh3hcsc740w4ml
[2] https://www.mail-archive.com/dev@flink.apache.org/msg56702.html
[3] https://cwiki.apache.org/confluence/display/FLINK/1.16+Release

Martijn Visser  于2022年7月5日周二 17:32写道：

> Hi everyone,
>
> We've just finished our 1.16 release sync update and would like to update
> you on the current status and request for your help:
>
> 1. The Flink 1.16 release branch is expected to be cut in 3 weeks, which
> means that we will cut the release branch and start with the release
> testing. New features that didn't make that time will be postponed until
> the Flink release after this one.
>
> 2. Please help make it easier for the release managers by making sure that
> the Flink 1.16 release page is updated [1]. This means that:
>
> * There should be a Jira link on the release page
> * This is assigned to someone
> * The release page has the latest state reflected
> * When a Jira ticket is completed, proper release notes have been added to
> the Jira ticket.
>
> 3. There are numerous test instabilities which we need help with to get
> fixed. We currently have 1 release blocker and numerous critical test
> stability tickets open. You can see an overview of these also on the
> release page [2]. Please help the release managers with:
>
> * Volunteering to pick up a test instability ticket. You can ping me
> (martijnvisser) to get it assigned to you.
> * Please also mark the ticket as 'In Progress' when you're working on it
> and 'Stop Progress' if you're not working on it anymore, so that we know
> who is working on which ticket.
>
> Current open test instability tickets that needs a volunteer to review
> and/or create fix are https://issues.apache.org/jira/browse/FLINK-26979
> (reviewer), https://issues.apache.org/jira/browse/FLINK-28398,
> https://issues.apache.org/jira/browse/FLINK-28392 and
> https://issues.apache.org/jira/browse/FLINK-26402.
>
> Best regards,
>
> Martijn
>
> [1] https://cwiki.apache.org/confluence/display/FLINK/1.16+Release
> [2]
>
> https://cwiki.apache.org/confluence/display/FLINK/1.16+Release#id-1.16Release-2022-07-05
>

Re: [VOTE] Release 1.15.1, release candidate #1

[Xingbo Huang]

+1 (non-binding)

- verify signatures and checksums
- no binaries found in source archive
- build from source
- Reviewed the release note blog
- verify python wheel package contents
- pip install apache-flink-libraries and apache-flink wheel packages
- run the examples from Python Table API tutorial

Best,
Xingbo

Chesnay Schepler  于2022年6月24日周五 21:42写道：

> +1 (binding)
>
> - signatures OK
> - all required artifacts appear to be present
> - tag exists with the correct version adjustments
> - binary shows correct commit and version
> - examples run fine
> - website PR looks good
>
> On 22/06/2022 14:20, David Anderson wrote:
> > Hi everyone,
> >
> > Please review and vote on release candidate #1 for version 1.15.1, 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],
> > * the official Apache source release and binary convenience releases to
> be
> > deployed to dist.apache.org [2], which are signed with the key with
> > fingerprint E982F098 [3],
> > * all artifacts to be deployed to the Maven Central Repository [4],
> > * source code tag "release-1.15.1-rc1" [5],
> > * website pull request listing the new release and adding announcement
> blog
> > post [6].
> >
> > The vote will be open for at least 72 hours. It is adopted by majority
> > approval, with at least 3 PMC affirmative votes.
> >
> > Thanks,
> > David
> >
> > [1]
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=
> > 12351546
> > [2] https://dist.apache.org/repos/dist/dev/flink/flink-1.15.1-rc1/
> > [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> > [4]
> https://repository.apache.org/content/repositories/orgapacheflink-1511/
> > [5] https://github.com/apache/flink/tree/release-1.15.1-rc1
> > [6] https://github.com/apache/flink-web/pull/554
> >
>
>

Re: [DISCUSS] Releasing Flink ML 2.1.0

[Xingbo Huang]

Hi Yun and Zhipeng,

Thanks a lot for starting the discussion. +1 for the FLINK ML 2.1.0
release. Looking forward for these ML algorithms. I plan to write a blog
about PyFlink + Flink ML after the released.

Best,
Xingbo

Zhipeng Zhang  于2022年6月23日周四 11:15写道：

> Hi devs,
>
> Yun and I would like to start a discussion for releasing Flink ML
>  2.1.0.
>
> In the past few months, we focused on improving the infra (e.g. memory
> management, benchmark infra, online training, python support) of Flink ML
> by implementing, benchmarking, and optimizing 9 new algorithms in Flink ML.
> Our results have shown that Flink ML is able to meet or exceed the
> performance of selected algorithms in alternative popular ML libraries.
>
> Please see below for a detailed list of improvements:
>
> - A set of representative machine learning algorithms:
> - feature engineering
> - MinMaxScaler (https://issues.apache.org/jira/browse/FLINK-25552)
> - StringIndexer (https://issues.apache.org/jira/browse/FLINK-25527
> )
> - VectorAssembler (
> https://issues.apache.org/jira/browse/FLINK-25616
> )
> - StandardScaler (
> https://issues.apache.org/jira/browse/FLINK-26626)
> - Bucketizer (https://issues.apache.org/jira/browse/FLINK-27072)
> - online learning:
> - OnlineKmeans (https://issues.apache.org/jira/browse/FLINK-26313)
> - OnlineLogisiticRegression (
> https://issues.apache.org/jira/browse/FLINK-27170)
> - regression:
> - LinearRegression (
> https://issues.apache.org/jira/browse/FLINK-27093)
> - classification:
> - LinearSVC (https://issues.apache.org/jira/browse/FLINK-27091)
> - Evaluation:
> - BinaryClassificationEvaluator (
> https://issues.apache.org/jira/browse/FLINK-27294)
> - A benchmark framework for Flink ML. (
> https://issues.apache.org/jira/browse/FLINK-26443)
> - A website for Flink ML users (
> https://nightlies.apache.org/flink/flink-ml-docs-stable/)
> - Python support for Flink ML algorithms (
> https://issues.apache.org/jira/browse/FLINK-26268,
> https://issues.apache.org/jira/browse/FLINK-26269)
> - Several optimizations for FlinkML infrastructure (
> https://issues.apache.org/jira/browse/FLINK-27096,
> https://issues.apache.org/jira/browse/FLINK-27877)
>
> With the improvements and throughput benchmarks we have made, we think it
> is time to release Flink ML 2.1.0, so that interested developers in the
> community can try out the new Flink ML infra to develop algorithms with
> high throughput and low latency.
>
> If there is any concern, please let us know.
>
>
> Best,
> Yun and Zhipeng
>

[ANNOUNCE] Apache Flink 1.14.5 released

[Xingbo Huang]

The Apache Flink community is very happy to announce the release of Apache
Flink 1.14.5, which is the fourth bugfix release for the Apache Flink 1.14
series.

Apache Flink® is an open-source stream processing framework for
distributed, high-performing, always-available, and accurate data streaming
applications.

The release is available for download at:
https://flink.apache.org/downloads.html

Please check out the release blog post for an overview of the improvements
for this bugfix release:
https://flink.apache.org/news/2022/06/22/release-1.14.5.html

The full release notes are available in Jira:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12351388

We would like to thank all contributors of the Apache Flink community who
made this release possible!

Regards,
Xingbo

Re: [ANNOUNCE] New Apache Flink Committers: Qingsheng Ren, Shengkai Fang

[Xingbo Huang]

Congrats, Qingsheng and Shengkai!

Best,
Xingbo

Dian Fu  于2022年6月20日周一 18:52写道：

> Congratulations, Qingsheng and ShengKai!
>
> Regards,
> Dian
>
> On Mon, Jun 20, 2022 at 5:41 PM Lincoln Lee 
> wrote:
>
> > Congrats, Qingsheng and Shengkai!
> >
> >
> > Best,
> > Lincoln Lee
> >
> >
> > Sergey Nuyanzin  于2022年6月20日周一 17:24写道：
> >
> > > Congratulations, Qingsheng and ShengKai.
> > >
> > > On Mon, Jun 20, 2022 at 11:20 AM Feifan Wang 
> wrote:
> > >
> > > > Congratulations, Qingsheng and ShengKai.
> > > >
> > > >
> > > >
> > > > Best,
> > > > Feifan
> > > >
> > > >
> > > > ——
> > > > Name: Feifan Wang
> > > > Email: zoltar9...@163.com
> > > >
> > > >
> > > >  Replied Message 
> > > > | From | Zakelly Lan |
> > > > | Date | 06/20/2022 16:51 |
> > > > | To |  |
> > > > | Subject | Re: [ANNOUNCE] New Apache Flink Committers: Qingsheng
> Ren,
> > > > Shengkai Fang |
> > > > Congrats, Qingsheng and Shengkai.
> > > >
> > > > Best,
> > > > Zakelly
> > > >
> > > > On Mon, Jun 20, 2022 at 4:50 PM Geng Biao 
> wrote:
> > > >
> > > > Congrats to Qingsheng and Shengkai!
> > > > Best,
> > > > Biao Geng
> > > >
> > > > 获取 Outlook for iOS
> > > > 
> > > > 发件人: Zhilong Hong 
> > > > 发送时间: Monday, June 20, 2022 4:05:48 PM
> > > > 收件人: dev@flink.apache.org 
> > > > 抄送: Qingsheng Ren ; Shengkai Fang <
> > fskm...@gmail.com
> > > >
> > > > 主题: Re: [ANNOUNCE] New Apache Flink Committers: Qingsheng Ren,
> Shengkai
> > > > Fang
> > > >
> > > > Congratulations, Qingsheng and ShengKai!
> > > >
> > > > Best,
> > > > Zhilong.
> > > >
> > > > On Mon, Jun 20, 2022 at 4:00 PM Lijie Wang  >
> > > > wrote:
> > > >
> > > > Congratulations, Qingsheng and ShengKai.
> > > >
> > > > Best,
> > > > Lijie
> > > >
> > > > Paul Lam  于2022年6月20日周一 15:58写道：
> > > >
> > > > Congrats, Qingsheng and Shengkai!
> > > >
> > > > Best,
> > > > Paul Lam
> > > >
> > > > 2022年6月20日 15:57，Martijn Visser  写道：
> > > >
> > > > Congratulations to both of you, this is very much deserved!
> > > >
> > > > Op ma 20 jun. 2022 om 09:53 schreef Jark Wu :
> > > >
> > > > Hi everyone,
> > > >
> > > > On behalf of the PMC, I'm very happy to announce two new Flink
> > > > committers:
> > > > Qingsheng Ren and Shengkai Fang.
> > > >
> > > > Qingsheng is the core contributor and maintainer of the Kafka
> > > > connector.
> > > > He continuously improved the existing connectors, debugged many
> > > > connector
> > > > testability issues, and worked on the connector testing framework.
> > > > Recently,
> > > > he is driving the work of FLIP-221 (caching lookup connector), which
> > > > is
> > > > crucial for SQL connectors.
> > > >
> > > > Shengkai has been continuously contributing to the Flink project for
> > > > two
> > > > years.
> > > > He mainly works on Flink SQL parts and drives several important
> > > > FLIPs,
> > > > e.g. FLIP-149 (upsert-kafka), FLIP-163 (SQL CLI Improvements),
> > > > FLIP-91 (SQL Gateway), and FLIP-223 (HiveServer2 Endpoint).
> > > > He is very active and helps many users on the mailing list.
> > > >
> > > > Please join me in welcoming them as committers!
> > > >
> > > > Cheers,
> > > > Jark Wu
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > > --
> > > Best regards,
> > > Sergey
> > >
> >
>

[RESULT] [VOTE] Release 1.14.5, release candidate #1

[Xingbo Huang]

Hi everyone,

I am pleased to announce that we have unanimously approved this release
candidate:

There are 6 approving votes, 3 of which are binding:
- Konstantin Knauf (binding)
- Xingbo Huang (non-binding)
- Dian Fu (binding)
- Shuiqiang Chen (non-binding)
- Lijie Wang (non-binding)
- Yun Gao (binding)

There are no disapproving votes.

Thank you for verifying the release candidate. I will now proceed to
finalize the release and announce it once everything is published.

Best,
Xingbo

Re: [VOTE] Release 1.14.5, release candidate #1

[Xingbo Huang]

+1 (non-binding)

- verify signatures and checksums
- no binaries found in source archive
- build from source
- verify python wheel package contents
- pip install apache-flink-libraries and apache-flink wheel packages
- run the examples from Python Table API tutorial

Best,
Xingbo

Konstantin Knauf  于2022年6月12日周日 00:16写道：

> +1 (binding)
>
> * checked signatures and checksums of binaries -> OK
> * skimmed over changes since 1.14.4 -> no dependency updates without NOTICE
> updates
> * reviewed release blog post and -> requested changes
>
> Thanks for preparing this rc!
>
> Konstantin
>
>
> Am Fr., 10. Juni 2022 um 11:58 Uhr schrieb Xingbo Huang <
> hxbks...@gmail.com
> >:
>
> > Hi everyone,
> >
> > Please review and vote on the release candidate #1 for the version
> 1.14.5,
> > 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],
> > * the official Apache source release and binary convenience releases to
> be
> > deployed to dist.apache.org [2], which are signed with the key with
> > fingerprint 3C2C9FFB59DF9F3E [3],
> > * all artifacts to be deployed to the Maven Central Repository [4],
> > * source code tag "release-1.14.5-rc1" [5],
> > * website pull request listing the new release and adding announcement
> blog
> > post [6].
> >
> > The vote will be open for at least 72 hours. It is adopted by majority
> > approval, with at least 3 PMC affirmative votes.
> >
> > Best,
> > Xingbo
> >
> > [1]
> >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12351388
> > [2] https://dist.apache.org/repos/dist/dev/flink/flink-1.14.5-rc1/
> > [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> > [4]
> > https://repository.apache.org/content/repositories/orgapacheflink-1509/
> > [5] https://github.com/apache/flink/tree/release-1.14.5-rc1
> > [6] https://github.com/apache/flink-web/pull/550
> >
>
>
> --
> https://twitter.com/snntrable
> https://github.com/knaufk
>

Re: [VOTE] FLIP-228: Support Within between events in CEP Pattern

[Xingbo Huang]

+1 (binding)

Best,
Xingbo

Dian Fu  于2022年6月13日周一 16:08写道：

> +1 (binding)
>
> Regards,
> Dian
>
> On Mon, Jun 13, 2022 at 3:55 PM Rui Fan <1996fan...@gmail.com> wrote:
>
> > Thanks for Nicholas driving this.
> >
> > +1(non-binding)
> >
> > Best,
> > Rui Fan
> >
> > On Mon, Jun 13, 2022 at 3:05 PM md peng  wrote:
> >
> > > +1(not-binding)
> > >
> > > Best,
> > > Mingde Peng
> > >
> > > Martijn Visser  于2022年6月13日周一 14:48写道：
> > >
> > > > +1 (binding)
> > > >
> > > > Looking forward :)
> > > >
> > > > Thanks, Martijn
> > > >
> > > > Op ma 13 jun. 2022 om 04:16 schreef Nicholas :
> > > >
> > > > > Hi everyone，
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Thanks for feedback for FLIP-228: Support Within between events in
> > CEP
> > > > > Pattern[1] on the discussion thread[2]. I'd like to start a VOTE
> > thread
> > > > for
> > > > > FLIP-228.
> > > > >
> > > > > The vote will be open for at least 72 hours unless there is an
> > > objection
> > > > > or not enough votes.
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Regards,
> > > > >
> > > > > Nicholas Jiang
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > [1]
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-228%3A+Support+Within+between+events+in+CEP+Pattern
> > > > >
> > > > > [2]
> https://lists.apache.org/thread/p60ctx213f8921rgklk5f0b6xfrs8ksz
> > > >
> > >
> >
>

Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee

[Xingbo Huang]

Congratulations, Jingsong!

Best,
Xingbo

Jane Chan  于2022年6月13日周一 17:23写道：

> Congratulations, Jingsong!
>
> Best,
> Jane Chan
>
> On Mon, Jun 13, 2022 at 4:43 PM Shuo Cheng  wrote:
>
> > Congratulations, Jingsong!
> >
> > On 6/13/22, Paul Lam  wrote:
> > > Congrats, Jingsong! Well deserved!
> > >
> > > Best,
> > > Paul Lam
> > >
> > >> 2022年6月13日 16:31，Lincoln Lee  写道：
> > >>
> > >> Congratulations, Jingsong!
> > >>
> > >> Best,
> > >> Lincoln Lee
> > >>
> > >>
> > >> Jark Wu  于2022年6月13日周一 16:29写道：
> > >>
> > >>> Congrats, Jingsong!
> > >>>
> > >>> Cheers,
> > >>> Jark
> > >>>
> > >>> On Mon, 13 Jun 2022 at 16:16, Jiangang Liu <
> liujiangangp...@gmail.com>
> > >>> wrote:
> > >>>
> >  Congratulations, Jingsong!
> > 
> >  Best,
> >  Jiangang Liu
> > 
> >  Martijn Visser  于2022年6月13日周一 16:06写道：
> > 
> > > Like everyone has mentioned, this is very well deserved.
> > >>> Congratulations!
> > >
> > > Op ma 13 jun. 2022 om 09:57 schreef Benchao Li <
> libenc...@apache.org
> > >:
> > >
> > >> Congratulations, Jingsong!  Well deserved.
> > >>
> > >> Rui Fan <1996fan...@gmail.com> 于2022年6月13日周一 15:53写道：
> > >>
> > >>> Congratulations, Jingsong!
> > >>>
> > >>> Best,
> > >>> Rui Fan
> > >>>
> > >>> On Mon, Jun 13, 2022 at 3:40 PM LuNing Wang <
> wang4lun...@gmail.com
> > 
> > >> wrote:
> > >>>
> >  Congratulations, Jingsong!
> > 
> >  Best,
> >  LuNing Wang
> > 
> >  Ingo Bürk  于2022年6月13日周一 15:36写道：
> > 
> > > Congrats, Jingsong!
> > >
> > > On 13.06.22 08:58, Becket Qin wrote:
> > >> Hi all,
> > >>
> > >> I'm very happy to announce that Jingsong Lee has joined the
> >  Flink
> > >>> PMC!
> > >>
> > >> Jingsong became a Flink committer in Feb 2020 and has been
> > >>> continuously
> > >> contributing to the project since then, mainly in Flink SQL.
> > >>> He
> > > has
> >  been
> > >> quite active in the mailing list, fixing bugs, helping
> >  verifying
> > > releases,
> > >> reviewing patches and FLIPs. Jingsong is also devoted to
> >  pushing
> > >>> Flink
> > > SQL
> > >> to new use cases. He spent a lot of time in implementing the
> > > Flink
> > >> connectors for Apache Iceberg. Jingsong is also the primary
> > > driver
> >  behind
> > >> the effort of flink-table-store, which aims to provide a
> > >> stream-batch
> > >> unified storage for Flink dynamic tables.
> > >>
> > >> Congratulations and welcome, Jingsong!
> > >>
> > >> Cheers,
> > >>
> > >> Jiangjie (Becket) Qin
> > >> (On behalf of the Apache Flink PMC)
> > >>
> > >
> > 
> > >>>
> > >>
> > >>
> > >> --
> > >>
> > >> Best,
> > >> Benchao Li
> > >>
> > >
> > 
> > >>>
> > >
> > >
> >
>

[VOTE] Release 1.14.5, release candidate #1

[Xingbo Huang]

Hi everyone,

Please review and vote on the release candidate #1 for the version 1.14.5,
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],
* the official Apache source release and binary convenience releases to be
deployed to dist.apache.org [2], which are signed with the key with
fingerprint 3C2C9FFB59DF9F3E [3],
* all artifacts to be deployed to the Maven Central Repository [4],
* source code tag "release-1.14.5-rc1" [5],
* website pull request listing the new release and adding announcement blog
post [6].

The vote will be open for at least 72 hours. It is adopted by majority
approval, with at least 3 PMC affirmative votes.

Best,
Xingbo

[1]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12351388
[2] https://dist.apache.org/repos/dist/dev/flink/flink-1.14.5-rc1/
[3] https://dist.apache.org/repos/dist/release/flink/KEYS
[4] https://repository.apache.org/content/repositories/orgapacheflink-1509/
[5] https://github.com/apache/flink/tree/release-1.14.5-rc1
[6] https://github.com/apache/flink-web/pull/550

Re: [DISCUSS] Releasing 1.15.1

[Xingbo Huang]

Hi David,

+1
Thank you for driving this.

Best,
Xingbo

Chesnay Schepler  于2022年6月8日周三 18:41写道：

> +1
>
> Thank you for proposing this. I can take care of the PMC-side of things.
>
> On 08/06/2022 12:37, Jingsong Li wrote:
> > +1
> >
> > Thanks David for volunteering to manage the release.
> >
> > Best,
> > Jingsong
> >
> > On Wed, Jun 8, 2022 at 6:21 PM Jark Wu  wrote:
> >> Hi David, thank you for driving the release.
> >>
> >> +1 for the 1.15.1 release. The release-1.15 branch
> >> already contains many bug fixes and some SQL
> >> issues are quite critical.
> >>
> >> Btw, FLINK-27606 has been merged just now.
> >>
> >> Best,
> >> Jark
> >>
> >>
> >> On Wed, 8 Jun 2022 at 17:40, David Anderson 
> wrote:
> >>
> >>> I would like to start a discussion on releasing 1.15.1. Flink 1.15 was
> >>> released on the 5th of May [1] and so far 43 issues have been resolved,
> >>> including several user-facing issues with blocker and critical
> priorities
> >>> [2]. (The recent problem with FileSink rolling policies not working
> >>> properly in 1.15.0 got me thinking it might be time for bug-fix
> release.)
> >>>
> >>> There currently remain 16 unresolved tickets with a fixVersion of
> 1.15.1
> >>> [3], five of which are about CI infrastructure and tests. There is
> only one
> >>> such ticket marked Critical:
> >>>
> >>> https://issues.apache.org/jira/browse/FLINK-27492 Flink table scala
> >>> example
> >>> does not including the scala-api jars
> >>>
> >>> I'm not convinced we should hold up a release for this issue, but on
> the
> >>> other hand, it seems that this issue can be resolved by making a
> decision
> >>> about how to handle the missing dependencies. @Timo Walther
> >>>  @yun_gao can you give an update?
> >>>
> >>> Two other open issues seem to have made significant progress (listed
> >>> below). Would it make sense to wait for either of these? Are there any
> >>> other open tickets we should consider waiting for?
> >>>
> >>> https://issues.apache.org/jira/browse/FLINK-27420 Suspended
> SlotManager
> >>> fail to reregister metrics when started again
> >>> https://issues.apache.org/jira/browse/FLINK-27606 CompileException
> when
> >>> using UDAF with merge() method
> >>>
> >>> I would volunteer to manage the release. Is there a PMC member who
> would
> >>> join me to help, as needed?
> >>>
> >>> Best,
> >>> David
> >>>
> >>> [1] https://flink.apache.org/news/2022/05/05/1.15-announcement.html
> >>>
> >>> [2]
> >>>
> >>>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLINK%20AND%20status%20in%20%20(Resolved%2C%20Closed)%20AND%20fixVersion%20%3D%201.15.1%20ORDER%20BY%20priority%20DESC%2C%20created%20DESC
> >>>
> >>> [3]
> >>>
> >>>
> https://issues.apache.org/jira/browse/FLINK-27492?jql=project%20%3D%20FLINK%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20fixVersion%20%3D%201.15.1%20ORDER%20BY%20priority%20DESC%2C%20created%20DESC
> >>>
>
>

Re: [DISCUSS] Releasing Flink 1.14.5

[Xingbo Huang]

Hi everyone,

I will start with the preparation for the release.

Best,
Xingbo

Jing Ge  于2022年5月31日周二 01:20写道：

> Hi Xingbo,
>
> +1
> Thanks for driving this.
>
> Best regards,
> Jing
>
> On Mon, May 30, 2022 at 4:51 PM Martijn Visser 
> wrote:
>
> > Hi Xingbo,
> >
> > +1 to release Flink 1.14.5.
> >
> > Best regards,
> >
> > Martijn
> >
> > Op do 26 mei 2022 om 10:19 schreef Dian Fu :
> >
> > > Hi Xingbo,
> > >
> > > Thanks for driving this release. +1 for 1.14.5 as there are already
> > nearly
> > > 100 commits [1] since 1.14.4.
> > >
> > > Regards,
> > > Dian
> > >
> > > [1]
> > https://github.com/apache/flink/compare/release-1.14.4...release-1.14
> > >
> > > On Tue, May 24, 2022 at 2:23 PM Xingbo Huang 
> wrote:
> > >
> > > > Hi all,
> > > >
> > > > I would like to start discussing releasing Flink 1.14.5.
> > > >
> > > > It has already been more than two months since we released 1.14.4.
> > There
> > > > are currently 62 tickets[1] already resolved for 1.14.5, some of them
> > > quite
> > > > severe.
> > > >
> > > > Currently, there are no issues marked as critical or blocker for
> > 1.14.5.
> > > > Please let me know if there are any issues you'd like to be included
> in
> > > > this release but still not merged.
> > > >
> > > > I would like to volunteer as a release manager for 1.14.5, and start
> > the
> > > > release process once all the issues are merged.
> > > >
> > > > Best,
> > > > Xingbo
> > > >
> > > > [1]
> > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLINK%20AND%20fixVersion%20%3D%201.14.5=50
> > > >
> > >
> >
>

Re: [ANNOUNCE] Welcome to join the Apache Flink community on Slack

[Xingbo Huang]

Thanks everyone for the great effort driving this.

+1 for building a dedicated channel for CI builds.

Best,
Xingbo

Martijn Visser  于2022年6月8日周三 01:32写道：

> Hi Matthias,
>
> I've only thought about it, but I absolutely would +1 this. Making this
> information available in dedicated channels will only improve things.
>
> Best regards,
>
> Martijn
>
> Op di 7 jun. 2022 om 18:12 schreef Matthias Pohl :
>
> > Thanks for driving the Slack channel efforts and setting everything up.
> :-)
> >
> > I'm wondering whether we should extend the Slack space to also have a
> > channel dedicated for CI builds to enable the release managers to monitor
> > CI builds on master and the release branches through the Apache Flink
> Slack
> > workspace. It might help us in being more transparent with the release
> > process. The same goes for the Flink performance tests [1].
> >
> > Are there plans around that already? I couldn't find anything related in
> > [2]. Or is it worth opening another thread around that topic.
> >
> > Best,
> > Matthias
> >
> > [1]
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=115511847
> > [2] https://cwiki.apache.org/confluence/display/FLINK/Slack+Management
> > On Tue, Jun 7, 2022 at 10:39 AM Jing Ge  wrote:
> >
> > > got it, thanks Martijn!
> > >
> > > Best regards,
> > > Jing
> > >
> > >
> > > On Tue, Jun 7, 2022 at 10:38 AM Martijn Visser <
> martijnvis...@apache.org
> > >
> > > wrote:
> > >
> > > > Hi Jing,
> > > >
> > > > Yes, since this Flink Community workspace is treated as one company.
> So
> > > > everyone you want to invite, should considered a 'coworker'.
> > > >
> > > > Best regards,
> > > >
> > > > Martijn
> > > >
> > > > Op za 4 jun. 2022 om 20:02 schreef Jing Ge :
> > > >
> > > >> Hi Xingtong,
> > > >>
> > > >> While inviting new members, there are two options: "From another
> > > company"
> > > >> vs "Your coworker". In this case, we should always choose "Your
> > > coworker"
> > > >> to add new members to the Apache Flink workspace, right?
> > > >>
> > > >> Best regards,
> > > >> Jing
> > > >>
> > > >> On Fri, Jun 3, 2022 at 1:10 PM Yuan Mei 
> > wrote:
> > > >>
> > > >>> Thanks, Xintong and Jark the great effort driving this, and
> everyone
> > > for
> > > >>> making this possible.
> > > >>>
> > > >>> I've also Twittered this announcement on our Apache Flink Twitter
> > > >>> account.
> > > >>>
> > > >>> Best
> > > >>>
> > > >>> Yuan
> > > >>>
> > > >>>
> > > >>>
> > > >>> On Fri, Jun 3, 2022 at 12:54 AM Jing Ge 
> wrote:
> > > >>>
> > >  Thanks everyone for your effort!
> > > 
> > >  Best regards,
> > >  Jing
> > > 
> > >  On Thu, Jun 2, 2022 at 4:17 PM Martijn Visser <
> > > martijnvis...@apache.org>
> > >  wrote:
> > > 
> > > > Thanks everyone for joining! It's good to see so many have joined
> > in
> > > > such a short time already. I've just refreshed the link which you
> > can
> > > > always find on the project website [1]
> > > >
> > > > Best regards, Martijn
> > > >
> > > > [1] https://flink.apache.org/community.html#slack
> > > >
> > > > Op do 2 jun. 2022 om 11:42 schreef Jingsong Li <
> > > jingsongl...@gmail.com
> > > > >:
> > > >
> > > >> Thanks Xingtong, Jark, Martijn and Robert for making this
> > possible!
> > > >>
> > > >> Best,
> > > >> Jingsong
> > > >>
> > > >>
> > > >> On Thu, Jun 2, 2022 at 5:32 PM Jark Wu 
> wrote:
> > > >>
> > > >>> Thank Xingtong for making this possible!
> > > >>>
> > > >>> Cheers,
> > > >>> Jark Wu
> > > >>>
> > > >>> On Thu, 2 Jun 2022 at 15:31, Xintong Song <
> tonysong...@gmail.com
> > >
> > > >>> wrote:
> > > >>>
> > > >>> > Hi everyone,
> > > >>> >
> > > >>> > I'm very happy to announce that the Apache Flink community
> has
> > > >>> created a
> > > >>> > dedicated Slack workspace [1]. Welcome to join us on Slack.
> > > >>> >
> > > >>> > ## Join the Slack workspace
> > > >>> >
> > > >>> > You can join the Slack workspace by either of the following
> two
> > > >>> ways:
> > > >>> > 1. Click the invitation link posted on the project website
> [2].
> > > >>> > 2. Ask anyone who already joined the Slack workspace to
> invite
> > > you.
> > > >>> >
> > > >>> > We recommend 2), if available. Due to Slack limitations, the
> > > >>> invitation
> > > >>> > link in 1) expires and needs manual updates after every 100
> > > >>> invites. If it
> > > >>> > is expired, please reach out to the dev / user mailing lists.
> > > >>> >
> > > >>> > ## Community rules
> > > >>> >
> > > >>> > When using the community Slack workspace, please follow these
> > > >>> community
> > > >>> > rules:
> > > >>> > * *Be respectful* - This is the most important rule!
> > > >>> > * All important decisions and conclusions *must be reflected
> > back
> > > >>> to the
> > > >>> > mailing lists*. "If 

[DISCUSS] Releasing Flink 1.14.5

[Xingbo Huang]

Hi all,

I would like to start discussing releasing Flink 1.14.5.

It has already been more than two months since we released 1.14.4. There
are currently 62 tickets[1] already resolved for 1.14.5, some of them quite
severe.

Currently, there are no issues marked as critical or blocker for 1.14.5.
Please let me know if there are any issues you'd like to be included in
this release but still not merged.

I would like to volunteer as a release manager for 1.14.5, and start the
release process once all the issues are merged.

Best,
Xingbo

[1]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLINK%20AND%20fixVersion%20%3D%201.14.5=50

Re: [DISCUSS] Planning Flink 1.16

[Xingbo Huang]

Thanks Konstantin and Chesnay for starting the discussion. I'm also willing
to volunteer as the release manager if this is still open.

Regarding the feature freeze date, +1 to the end of mid August.

Best,
Xingbo

Zhu Zhu  于2022年4月29日周五 11:01写道：

> +1 for a 5 months release cycle.
> +1 target the feature freeze date 1.5 months before the release date. It
> can better guard the release date.
> Therefore, also +1 for mid August as the feature freeze date of 1.16
>
> Thanks,
> Zhu
>
> Jark Wu  于2022年4月28日周四 22:24写道：
>
> > I'm also fine with the end of July for the feature freeze.
> >
> > Best,
> > Jark
> >
> > On Thu, 28 Apr 2022 at 21:00, Martijn Visser 
> > wrote:
> >
> > > +1 for continuing to strive for a 5 months release cycle.
> > >
> > > And +1 to have the planned feature freeze mid August, which I would
> > propose
> > > to have happen on Monday the 15th of August 2022. I would also already
> > > state that even though we know this is a holiday period, we should not
> > > extend this deadline for that reason :)
> > >
> > > Best regards,
> > >
> > > Martijn Visser
> > > https://twitter.com/MartijnVisser82
> > > https://github.com/MartijnVisser
> > >
> > >
> > > On Thu, 28 Apr 2022 at 14:37, Jingsong Li 
> > wrote:
> > >
> > > > Thanks for the check.
> > > >
> > > > > Continue to strive for a 5 months release cycle and 1.5 months
> before
> > > to
> > > > the desired release date
> > > >
> > > > Sounds good to me!
> > > >
> > > > Best,
> > > > Jingsong
> > > >
> > > > On Thu, Apr 28, 2022 at 7:06 PM Konstantin Knauf 
> > > > wrote:
> > > > >
> > > > > Hi everyone,
> > > > >
> > > > > thank you for the feedback so far. I've checked the length of the
> > > > previous
> > > > > last release cycles. Up until Flink 1.14, we've actually been
> > > incredibly
> > > > > good at maintaining a 5 months release cycle (see below).
> > > Interestingly,
> > > > > the community is officially targeting a 4 months release cycle [1].
> > > > >
> > > > > - 1.15.0 2022-05-01? (7 months, 2 days?)
> > > > > - 1.14.0: 2021-09-29 (4 months, 26 days)
> > > > > - 1.13.0: 2021-05-03 (4 months, 23 days)
> > > > > - 1.12.0: 2020-12-10 (5 months, 3 days)
> > > > > - 1.11.0: 2020-07-07 (4 months, 26 days)
> > > > > - 1.10.0: 2020-02-11
> > > > >
> > > > > The 1.15 release cycle has took significantly longer. In my opinion
> > we
> > > > > should try to get back into the 5 months cadence with the next
> > release.
> > > > > Since empirically we always often end up moving the the feature
> > freeze
> > > > by a
> > > > > week or two, and that we often need about a month for release
> > testing &
> > > > > stabilization and releasing, I don't think, we should move the
> > planned
> > > > > feature freeze to later than
> > > > > *mid August. *
> > > > > What do you think:
> > > > > 1. Should we continue to strive for a 5 months release cycle (and
> > > update
> > > > > [1] accordingly)?
> > > > > 2. Does it sound reasonable to target a feature freeze date, which
> is
> > > 1.5
> > > > > months before to the desired release date?
> > > > >
> > > > > Cheers,
> > > > >
> > > > > Konstantin
> > > > >
> > > > >  [1]
> > > >
> https://cwiki.apache.org/confluence/display/FLINK/Time-based+releases
> > > > >
> > > > > Am Do., 28. Apr. 2022 um 05:20 Uhr schrieb Jingsong Li <
> > > > > jingsongl...@gmail.com>:
> > > > >
> > > > > > Thanks Konstantin and Chesnay for starting the discussion. And
> > thanks
> > > > > > Konstantin, Chesnay, Godfrey, Martijn for volunteering.
> > > > > >
> > > > > > The 1.16 release at the end of July means that there are
> currently
> > > > > > only 3 months to fully commit to 1.16 development, and I'm a
> little
> > > > > > concerned that this is too short a time frame, which may result
> in
> > > > > > some features only reaching a halfway decent state.
> > > > > >
> > > > > > Best,
> > > > > > Jingsong
> > > > > >
> > > > > >
> > > > > > On Wed, Apr 27, 2022 at 7:10 PM David Morávek 
> > > wrote:
> > > > > > >
> > > > > > > Thanks Konstantin and Chesnay for starting the discussion and
> > > > > > volunteering.
> > > > > > > The timeline proposal sounds reasonable :+1:
> > > > > > >
> > > > > > > Best,
> > > > > > > D.
> > > > > > >
> > > > > > > On Tue, Apr 26, 2022 at 1:37 PM Martijn Visser <
> > > > martijnvis...@apache.org
> > > > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Hi everyone,
> > > > > > > >
> > > > > > > > Thanks for starting this discussion. I would also volunteer
> to
> > > help
> > > > > > out as
> > > > > > > > a release manager for the 1.16 release.
> > > > > > > >
> > > > > > > > Best regards,
> > > > > > > >
> > > > > > > > Martijn Visser
> > > > > > > > https://twitter.com/MartijnVisser82
> > > > > > > > https://github.com/MartijnVisser
> > > > > > > >
> > > > > > > >
> > > > > > > > On Tue, 26 Apr 2022 at 13:19, godfrey he <
> godfre...@gmail.com>
> > > > wrote:
> > > > > > > >
> > > > > > > > > Hi Konstantin & Chesnay,
> > > > > > > > >
> > > > > > > > > Thanks for driving 

Re: [VOTE] Release 1.15.0, release candidate #4

[Xingbo Huang]

+1 (non-binding)

- Verified checksums and signatures
- Verified Python wheel package contents
- Pip install apache-flink-libraries source package and apache-flink wheel
package in Mac/Linux
- Run the examples from Python Table API Tutorial in Python REPL
- Test the Python UDF jobs in Thread Mode.

Best,
Xingbo

Dawid Wysakowicz  于2022年4月21日周四 18:52写道：

> +1 (binding),
>
>- checked licenses diff to my previous checks on rc2, this time
>everything seems ok
>- checked checksums, signatures, there are no binaries
>- compiled from sources
>- run a standalone cluster, clicked through the UI
>- run StateMachineExample took a savepoint in native format and
>stopped with a savepoint in native format
>
> Best,
>
> Dawid
> On 21/04/2022 05:49, Yun Gao wrote:
>
> Hi everyone,
>
> Please review and vote on the release candidate #4 for the version 1.15.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],* the official Apache source release and binary 
> convenience releases to be deployed to dist.apache.org [2],
>which are signed with the key with fingerprint 
> CBE82BEFD827B08AFA843977EDBF922A7BC84897 [3],
> * all artifacts to be deployed to the Maven Central Repository [4],
> * source code tag "release-1.15.0-rc4" [5],* website pull request listing the 
> new release and adding announcement blog post [6].
>
> The vote will be open for at least 72 hours. It is adopted by majority
> approval, with at least 3 PMC affirmative votes.
>
> Thanks,
> Joe, Till and Yun Gao
>
> [1] 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12350442
> [2] https://dist.apache.org/repos/dist/dev/flink/flink-1.15.0-rc4/
> [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> [4] https://repository.apache.org/content/repositories/orgapacheflink-1500/
> [5] https://github.com/apache/flink/releases/tag/release-1.15.0-rc4/
> [6] https://github.com/apache/flink-web/pull/526
>
>

Re: Issue while running word_count.py

[Xingbo Huang]

Hi Rohith,

I guess the `word_count.py` you tried to execute is from flink release-1.15
or master branch. For pyflink 1.14 you are using, you need to change
`t_env.get_config().set_string("parallelism.default", "1")` to
`t_env.get_config().get_configuration().set_string("parallelism.default",
"1")`

Best,
Xingbo

Rohith Vallu  于2022年4月22日周五 09:40写道：

> Hi,
>
> I set up pyflink on my system for python version 3.7.5 and pyflink version
> 1.14.4.
> When i try to run word_count.py using command "python word_count.py" I get
> this error
>
> Traceback (most recent call last):
>   File "word_count.py", line 146, in 
> word_count(known_args.input, known_args.output)
>   File "word_count.py", line 68, in word_count
> t_env.get_config().set_string("parallelism.default", "1")
> AttributeError: 'TableConfig' object has no attribute 'set'
>
> Can you help in resolving this issue?
>
> Best
> Rohith.
>

Re: pyflink on Python 3.9 dev guide

[Xingbo Huang]

link.client.program.PackagedProgram.invokeInteractiveModeForExecution(PackagedProgram.java:222)
> ~[flink-dist_2.11-1.14.3.jar:1.14.3]
> at
> org.apache.flink.client.ClientUtils.executeProgram(ClientUtils.java:114)
> ~[flink-dist_2.11-1.14.3.jar:1.14.3]
> at
>
> org.apache.flink.client.cli.CliFrontend.executeProgram(CliFrontend.java:812)
> ~[flink-dist_2.11-1.14.3.jar:1.14.3]
> at
> org.apache.flink.client.cli.CliFrontend.run(CliFrontend.java:246)
> ~[flink-dist_2.11-1.14.3.jar:1.14.3]
> at
> org.apache.flink.client.cli.CliFrontend.parseAndRun(CliFrontend.java:1054)
> ~[flink-dist_2.11-1.14.3.jar:1.14.3]
> at
>
> org.apache.flink.client.cli.CliFrontend.lambda$main$10(CliFrontend.java:1132)
> ~[flink-dist_2.11-1.14.3.jar:1.14.3]
> at
>
> org.apache.flink.runtime.security.contexts.NoOpSecurityContext.runSecured(NoOpSecurityContext.java:28)
> [flink-dist_2.11-1.14.3.jar:1.14.3]
> at
> org.apache.flink.client.cli.CliFrontend.main(CliFrontend.java:1132)
> [flink-dist_2.11-1.14.3.jar:1.14.3]
> 08:14:10.129 [main] ERROR org.apache.flink.client.cli.CliFrontend - Fatal
> error while running command line interface.
> org.apache.flink.client.program.ProgramAbortException:
> java.lang.RuntimeException: Python process exits with code: 1
> at
> org.apache.flink.client.python.PythonDriver.main(PythonDriver.java:140)
> ~[?:?]
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method) ~[?:?]
> at
>
> jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> ~[?:?]
> at
>
> jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> ~[?:?]
> at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]
> at
>
> org.apache.flink.client.program.PackagedProgram.callMainMethod(PackagedProgram.java:355)
> ~[flink-dist_2.11-1.14.3.jar:1.14.3]
> at
>
> org.apache.flink.client.program.PackagedProgram.invokeInteractiveModeForExecution(PackagedProgram.java:222)
> ~[flink-dist_2.11-1.14.3.jar:1.14.3]
> at
> org.apache.flink.client.ClientUtils.executeProgram(ClientUtils.java:114)
> ~[flink-dist_2.11-1.14.3.jar:1.14.3]
> at
>
> org.apache.flink.client.cli.CliFrontend.executeProgram(CliFrontend.java:812)
> ~[flink-dist_2.11-1.14.3.jar:1.14.3]
> at
> org.apache.flink.client.cli.CliFrontend.run(CliFrontend.java:246)
> ~[flink-dist_2.11-1.14.3.jar:1.14.3]
> at
> org.apache.flink.client.cli.CliFrontend.parseAndRun(CliFrontend.java:1054)
> ~[flink-dist_2.11-1.14.3.jar:1.14.3]
> at
>
> org.apache.flink.client.cli.CliFrontend.lambda$main$10(CliFrontend.java:1132)
> ~[flink-dist_2.11-1.14.3.jar:1.14.3]
> at
>
> org.apache.flink.runtime.security.contexts.NoOpSecurityContext.runSecured(NoOpSecurityContext.java:28)
> ~[flink-dist_2.11-1.14.3.jar:1.14.3]
> at
> org.apache.flink.client.cli.CliFrontend.main(CliFrontend.java:1132)
> [flink-dist_2.11-1.14.3.jar:1.14.3]
> Caused by: java.lang.RuntimeException: Python process exits with code: 1
> at
> org.apache.flink.client.python.PythonDriver.main(PythonDriver.java:130)
> ~[?:?]
> ... 13 more
> org.apache.flink.client.program.ProgramAbortException:
> java.lang.RuntimeException: Python process exits with code: 1
> at
> org.apache.flink.client.python.PythonDriver.main(PythonDriver.java:140)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> at
>
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
>
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at
>
> org.apache.flink.client.program.PackagedProgram.callMainMethod(PackagedProgram.java:355)
> at
>
> org.apache.flink.client.program.PackagedProgram.invokeInteractiveModeForExecution(PackagedProgram.java:222)
> at
> org.apache.flink.client.ClientUtils.executeProgram(ClientUtils.java:114)
> at
>
> org.apache.flink.client.cli.CliFrontend.executeProgram(CliFrontend.java:812)
> at
> org.apache.flink.client.cli.CliFrontend.run(CliFrontend.java:246)
> at
> org.apache.flink.client.cli.CliFrontend.parseAndRun(CliFrontend.java:1054)
> at
>
> org.apache.flink.client.cli.CliFrontend.lambda$main$10(CliFrontend.java:1132)
> at
>
> org.apache.flink.runtime.security.contexts.NoOpSecurityContext.runSecured(NoOpSecurityContext.java:28)
> at
> org.apache.flink.client.cli.CliFrontend.main(CliFrontend.j

Re: Regarding java.lang.NullPointerException

[Xingbo Huang]

Hi Josemon,

Can you provide the version of PyFlink you are using, and it would be
better if you can also provide code snippets that can be easily reproduced
this problem.

Best,
Xingbo

Josemon Maliakal  于2022年4月5日周二 13:31写道：

> Hello There,
> I started using pyflink recently,
> Have anyone know why I am getting java.lang.NullPointerException when I am
> trying to write an update function like the following
>
>  tbl = tbl.select(update_tel(tbl.data)).execute_insert('result').wait()
>
>
> Caused by: java.lang.NullPointerException
> at
>
> org.apache.beam.runners.core.construction.PipelineOptionsTranslation.toProto(PipelineOptionsTranslation.java:54)
> at
>
> org.apache.flink.streaming.api.runners.python.beam.BeamPythonFunctionRunner.open(BeamPythonFunctionRunner.java:230)
> at
>
> org.apache.flink.streaming.api.operators.python.AbstractPythonFunctionOperator.open(AbstractPythonFunctionOperator.java:131)
> at
>
> org.apache.flink.table.runtime.operators.python.AbstractStatelessFunctionOperator.open(AbstractStatelessFunctionOperator.java:110)
>
> at
>
> org.apache.flink.table.runtime.operators.python.scalar.AbstractPythonScalarFunctionOperator.open(AbstractPythonScalarFunctionOperator.java:100)
> at
>
> org.apache.flink.table.runtime.operators.python.scalar.PythonScalarFunctionOperator.open(PythonScalarFunctionOperator.java:62)
> at
>
> org.apache.flink.streaming.runtime.tasks.RegularOperatorChain.initializeStateAndOpenOperators(RegularOperatorChain.java:110)
> at
>
> org.apache.flink.streaming.runtime.tasks.StreamTask.restoreGates(StreamTask.java:711)
> at
>
> org.apache.flink.streaming.runtime.tasks.StreamTaskActionExecutor$1.call(StreamTaskActionExecutor.java:55)
> at
>
> org.apache.flink.streaming.runtime.tasks.StreamTask.restoreInternal(StreamTask.java:687)
> at
>
> org.apache.flink.streaming.runtime.tasks.StreamTask.restore(StreamTask.java:654)
> at
>
> org.apache.flink.runtime.taskmanager.Task.runWithSystemExitMonitoring(Task.java:958)
> at
> org.apache.flink.runtime.taskmanager.Task.restoreAndInvoke(Task.java:927)
> at org.apache.flink.runtime.taskmanager.Task.doRun(Task.java:766)
> at org.apache.flink.runtime.taskmanager.Task.run(Task.java:575)
> at java.base/java.lang.Thread.run(Thread.java:834)
>
>
>
> --
> *Regards, *
> *Josemon Maliakal*
> *+9605936925...@flink.apache.org <9605936925...@flink.apache.org>*
>