Re: Streaming data from AWS S3 Source

[Feng Jin]

Hi Neelabh

You can use  FileSystem Connector .  for DataStream [1]   for TableAPI [2]
.
And you need to put necessary  dependency to your flink environment. [3]

For Flink SQL setup, you can reference `sql getting started module`[4]

[1].
https://nightlies.apache.org/flink/flink-docs-master/docs/connectors/datastream/filesystem/#file-source
[2].
https://nightlies.apache.org/flink/flink-docs-master/docs/connectors/table/filesystem/
[3].
https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/filesystems/overview/
[4].
https://nightlies.apache.org/flink/flink-docs-master/docs/dev/table/sql/gettingstarted/#prerequisites


Best,
Feng

On Fri, Nov 24, 2023 at 1:52 PM Neelabh Shukla 
wrote:

> Hey Team,
> I want to stream data from AWS S3 source as they are being generated by an
> event to Apache Flink Stream for a data transformation job.
>
> I found out about FileSystem SQL Connector
> <
> https://stackoverflow.com/questions/62618381/apache-flink-with-s3-as-source-and-s3-as-sink
> >
> but
> need some reference on how to set this up.
>
> Feel free to share any learnings you have with this problem or any resource
> I can refer to.
>
> Based on slack recommendation I am reaching out to this email list but let
> me know if this is not the correct place to reach out to the community.
>
> Thanks,
> Neelabh
>

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

[Jing Ge]

+1(not-binding)

- verified signatures hash
- verified hash
- checked the tag
- checked the repo
- verified there are no binaries in the source archive
- built from sources

Best regards,
Jing

On Thu, Nov 23, 2023 at 7:44 PM Feng Jin  wrote:

> +1(non-binding)
>
> - verified signatures and hashsums
> - Verified there are no binaries in the source archive
> - Built Flink from sources
> - Started local standalone cluster, submitted sql job using sql-client
>
> Best,
> Feng
>
> On Thu, Nov 23, 2023 at 11:00 PM Hang Ruan  wrote:
>
> > +1 (non-binding)
> >
> > - verified signatures
> > - verified hashsums
> > - Verified there are no binaries in the source archive
> > - reviewed the Release Note
> > - reviewed the web PR
> >
> > Best,
> > Hang
> >
> > Jiabao Sun  于2023年11月23日周四 22:15写道：
> >
> > > Thanks for driving this release.
> > >
> > > +1 (non-binding)
> > >
> > > - Checked the tag in git
> > > - Verified signatures and hashsums
> > > - Verified there are no binaries in the source archive
> > > - Built Flink from sources
> > >
> > > Best,
> > > Jiabao
> > >
> > > > 2023年11月23日 21:55，Sergey Nuyanzin  写道：
> > > >
> > > > +1 (non-binding)
> > > >
> > > > - Downloaded artifacts
> > > > - Built Flink from sources
> > > > - Verified checksums & signatures
> > > > - Verified pom/NOTICE files
> > > > - reviewed the web PR
> > > >
> > > > On Thu, Nov 23, 2023 at 1:28 PM Leonard Xu 
> wrote:
> > > >
> > > >> +1 (binding)
> > > >>
> > > >> - verified signatures
> > > >> - verified hashsums
> > > >> - checked that all POM files point to the same version 1.16.3
> > > >> - started SQL Client, used MySQL CDC connector to read changelog
> from
> > > >> database , the result is expected
> > > >> - reviewed the web PR, left minor comment
> > > >>
> > > >> Best,
> > > >> Leonard
> > > >>
> > > >>> 2023年11月21日 下午8:56，Matthias Pohl 
> > 写道：
> > > >>>
> > > >>> +1 (binding)
> > > >>>
> > > >>> * Downloaded artifacts
> > > >>> * Built Flink from sources
> > > >>> * Verified SHA512 checksums & GPG signatures
> > > >>> * Compared checkout with provided sources
> > > >>> * Verified pom file versions
> > > >>> * Went over NOTICE/pom file changes without finding anything
> > suspicious
> > > >>> * Deployed standalone session cluster and ran WordCount example in
> > > batch
> > > >>> and streaming: Nothing suspicious in log files found
> > > >>> * Verified Java version of uploaded binaries
> > > >>>
> > > >>> Thanks for wrapping 1.16 up. :)
> > > >>>
> > > >>> On Tue, Nov 21, 2023 at 4:55 AM Rui Fan <1996fan...@gmail.com>
> > wrote:
> > > >>>
> > >  +1 (non-binding)
> > > 
> > >  Verified based on this wiki[1].
> > > 
> > >  - Verified signatures and sha512
> > >  - The source archives do not contain any binaries
> > >  - Build the source with Maven 3 and java8 (Checked the license as
> > > well)
> > >  - bin/start-cluster.sh with java8, it works fine and no any
> > unexpected
> > > >> LOG
> > >  - Ran demo, it's fine:  bin/flink run
> > >  examples/streaming/StateMachineExample.jar
> > > 
> > >  [1]
> > > 
> > > >>
> > >
> >
> https://cwiki.apache.org/confluence/display/FLINK/Verifying+a+Flink+Release
> > > 
> > >  Best,
> > >  Rui
> > > 
> > >  On Fri, Nov 17, 2023 at 11:52 AM Yun Tang 
> wrote:
> > > 
> > > > +1 (non-binding)
> > > >
> > > >
> > > > *   Verified signatures
> > > > *   Build from source code, and it looks good
> > > > *   Verified that jar packages are built with maven-3.2.5 and
> JDK8
> > > > *   Reviewed the flink-web PR
> > > > *   Start a local standalone cluster and submit examples
> > > >
> > > > Best
> > > > Yun Tang
> > > > 
> > > > From: Rui Fan <1996fan...@gmail.com>
> > > > Sent: Monday, November 13, 2023 18:20
> > > > To: dev 
> > > > Subject: [VOTE] Release 1.16.3, release candidate #1
> > > >
> > > > Hi everyone,
> > > >
> > > > Please review and vote on the release candidate #1 for the
> version
> > >  1.16.3,
> > > >
> > > > 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 B2D64016B940A7E0B9B72E0D7D0528B28037D8BC [3],
> > > >
> > > > * all artifacts to be deployed to the Maven Central Repository
> [4],
> > > >
> > > > * source code tag "release-1.16.3-rc1" [5],
> > > >
> > > > * website pull request listing the new release and adding
> > > announcement
> > >  blog
> > > > post [6].
> > > 

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

[Jing Ge]

+1(not-binding)

- verified signatures and hash
- reviewed the web PR
- checked the tag
- verified there are no binaries in the source archive
- built from sources

Best regards,
Jing

On Fri, Nov 24, 2023 at 4:07 AM weijie guo 
wrote:

> Sorry, it's a non-binding vote. :)
>
> Best regards,
>
> Weijie
>
>
> weijie guo  于2023年11月24日周五 11:05写道：
>
> > +1 (binding)
> >
> > - Verified signatures and hashsums
> > - Verified POM/NOTICE filess
> > - Built from sources.
> > - Reviewed the web PR.
> >
> > Best regards,
> >
> > Weijie
> >
> >
> > Yuxin Tan  于2023年11月24日周五 10:18写道：
> >
> >> +1 (non-binding)
> >>
> >> - Verified signatures and hashsums
> >> - Verified there are no binaries in the source archive
> >> - Built Flink from sources
> >> - Reviewed the web PR
> >>
> >> Best,
> >> Yuxin
> >>
> >>
> >> Feng Jin  于2023年11月24日周五 02:20写道：
> >>
> >> > +1(non-binding)
> >> >
> >> > - verified signatures and hashsums
> >> > - Verified there are no binaries in the source archive
> >> > - Built Flink from sources
> >> > - Started local standalone cluster, submitted sql job using sql-client
> >> >
> >> > Best,
> >> > Feng
> >> >
> >> >
> >> > On Thu, Nov 23, 2023 at 11:08 PM Hang Ruan 
> >> wrote:
> >> >
> >> > > +1 (non-binding)
> >> > >
> >> > > - verified signatures
> >> > > - verified hashsums
> >> > > - Verified there are no binaries in the source archive
> >> > > - reviewed the web PR
> >> > > - built Flink from sources
> >> > >
> >> > > Best,
> >> > > Hang
> >> > >
> >> > > Jiabao Sun  于2023年11月23日周四
> 22:09写道：
> >> > >
> >> > > > Thanks for driving this release.
> >> > > >
> >> > > > +1(non-binding)
> >> > > >
> >> > > > - Checked the tag in git
> >> > > > - Verified signatures and hashsums
> >> > > > - Verified there are no binaries in the source archive
> >> > > > - Built Flink from sources
> >> > > >
> >> > > > Best,
> >> > > > Jiabao
> >> > > >
> >> > > >
> >> > > > > 2023年11月21日 20:46，Matthias Pohl  .INVALID>
> >> 写道：
> >> > > > >
> >> > > > > +1 (binding)
> >> > > > >
> >> > > > > * Downloaded artifacts
> >> > > > > * Built Flink from sources
> >> > > > > * Verified SHA512 checksums & GPG signatures
> >> > > > > * Compared checkout with provided sources
> >> > > > > * Verified pom file versions
> >> > > > > * Went over NOTICE/pom file changes without finding anything
> >> > suspicious
> >> > > > > * Deployed standalone session cluster and ran WordCount example
> in
> >> > > batch
> >> > > > > and streaming: Nothing suspicious in log files found
> >> > > > > * Verified Java version of uploaded binaries
> >> > > > >
> >> > > > > Thanks Yun Tang for taking care of it.
> >> > > > >
> >> > > > > On Thu, Nov 16, 2023 at 7:02 AM Rui Fan <1996fan...@gmail.com>
> >> > wrote:
> >> > > > >
> >> > > > >> +1 (non-binding)
> >> > > > >>
> >> > > > >> - Verified signatures
> >> > > > >> - Reviewed the flink-web PR, left a couple of comments
> >> > > > >> - The source archives do not contain any binaries
> >> > > > >> - Build the source with Maven 3 and java8 (Checked the license
> as
> >> > > well)
> >> > > > >> - bin/start-cluster.sh with java8, it works fine and no any
> >> > unexpected
> >> > > > LOG
> >> > > > >> - Ran demo, it's fine:  bin/flink run
> >> > > > >> examples/streaming/StateMachineExample.jar
> >> > > > >>
> >> > > > >> Best,
> >> > > > >> Rui
> >> > > > >>
> >> > > > >> On Mon, Nov 13, 2023 at 4:04 PM Yun Tang 
> >> wrote:
> >> > > > >>
> >> > > > >>> Hi everyone,
> >> > > > >>>
> >> > > > >>> Please review and vote on the release candidate #1 for the
> >> version
> >> > > > >> 1.17.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 2E0E1AB5D39D55E608071FB9F795C02A4D2482B3 [3],
> >> > > > >>>
> >> > > > >>> * all artifacts to be deployed to the Maven Central Repository
> >> [4],
> >> > > > >>>
> >> > > > >>> * source code tag "release-1.17.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.
> >> > > > >>>
> >> > > > >>>
> >> > > > >>> [1]
> >> > > > >>>
> >> > > > >>
> >> > > >
> >> > >
> >> >
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353260
> >> > > > >>>
> >> > > > >>> [2]
> >> 

Streaming data from AWS S3 Source

[Neelabh Shukla]

Hey Team,
I want to stream data from AWS S3 source as they are being generated by an
event to Apache Flink Stream for a data transformation job.

I found out about FileSystem SQL Connector

but
need some reference on how to set this up.

Feel free to share any learnings you have with this problem or any resource
I can refer to.

Based on slack recommendation I am reaching out to this email list but let
me know if this is not the correct place to reach out to the community.

Thanks,
Neelabh

回复: Re:Re: [DISCUSS][FLINK-32993] Datagen connector handles length-constrained fields according to the schema definition by default

[lixin58...@163.com]

Thank Jane for providing examples to make discussions clearer.
Thank Lincoln and Xuyang for your feedback,I agree with you wholeheartedly that 
it is better to throw an error instead of ignoring it directly.
Extending datagen to generate variable length values is really an excelent 
idea, I will create another jira to follow up.

Taking the example provided,

  1.  For fixed-length data types (char, binary), two DDLs which custom length 
should throw exception like 'User-defined length of the fixed-length field f0 
is not supported.'

  1.
CREATE TABLE foo (
f0 CHAR(5)
) WITH ('connector' = 'datagen', 'fields.f0.length' = '10');

CREATE TABLE bar (
f0 CHAR(5)
) WITH ('connector' = 'datagen', 'fields.f0.length' = '1');

  1.  For variable-length data types (varchar, varbinary)，the first DDL can be 
executed legally, if illegal user-defined length configured, will throw 
exception like 'User-defined length of the VARCHAR field %s should be shorter 
than the schema definition.'

  1.
CREATE TABLE meow (
f0 VARCHAR(20)
) WITH ('connector' = 'datagen', 'fields.f0.length' = '10');

  1.  For special variable-length data types, since the length of String and 
Bytes is very large (2^31 - 1), when users does not specify a smaller field 
length, Fields that occupy a huge amount of memory (estimated to be more than 
2GB) will be generated by default, which can easily lead to 
"java.lang.OutOfMemoryError: Java heap space", so I recommend that the default 
length of these two fields is 100 just like before, but the length can be 
configured to less than 2^31-1.

  1.
CREATE TABLE purr (
f0 STRING
) WITH ('connector' = 'datagen', 'fields.f0.length' = '10');

Updates have been synchronized to the merge request [1]

WDYT?

[1] https://github.com/apache/flink/pull/23678


Best!
Yubin

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

[weijie guo]

Sorry, it's a non-binding vote. :)

Best regards,

Weijie


weijie guo  于2023年11月24日周五 11:05写道：

> +1 (binding)
>
> - Verified signatures and hashsums
> - Verified POM/NOTICE filess
> - Built from sources.
> - Reviewed the web PR.
>
> Best regards,
>
> Weijie
>
>
> Yuxin Tan  于2023年11月24日周五 10:18写道：
>
>> +1 (non-binding)
>>
>> - Verified signatures and hashsums
>> - Verified there are no binaries in the source archive
>> - Built Flink from sources
>> - Reviewed the web PR
>>
>> Best,
>> Yuxin
>>
>>
>> Feng Jin  于2023年11月24日周五 02:20写道：
>>
>> > +1(non-binding)
>> >
>> > - verified signatures and hashsums
>> > - Verified there are no binaries in the source archive
>> > - Built Flink from sources
>> > - Started local standalone cluster, submitted sql job using sql-client
>> >
>> > Best,
>> > Feng
>> >
>> >
>> > On Thu, Nov 23, 2023 at 11:08 PM Hang Ruan 
>> wrote:
>> >
>> > > +1 (non-binding)
>> > >
>> > > - verified signatures
>> > > - verified hashsums
>> > > - Verified there are no binaries in the source archive
>> > > - reviewed the web PR
>> > > - built Flink from sources
>> > >
>> > > Best,
>> > > Hang
>> > >
>> > > Jiabao Sun  于2023年11月23日周四 22:09写道：
>> > >
>> > > > Thanks for driving this release.
>> > > >
>> > > > +1(non-binding)
>> > > >
>> > > > - Checked the tag in git
>> > > > - Verified signatures and hashsums
>> > > > - Verified there are no binaries in the source archive
>> > > > - Built Flink from sources
>> > > >
>> > > > Best,
>> > > > Jiabao
>> > > >
>> > > >
>> > > > > 2023年11月21日 20:46，Matthias Pohl 
>> 写道：
>> > > > >
>> > > > > +1 (binding)
>> > > > >
>> > > > > * Downloaded artifacts
>> > > > > * Built Flink from sources
>> > > > > * Verified SHA512 checksums & GPG signatures
>> > > > > * Compared checkout with provided sources
>> > > > > * Verified pom file versions
>> > > > > * Went over NOTICE/pom file changes without finding anything
>> > suspicious
>> > > > > * Deployed standalone session cluster and ran WordCount example in
>> > > batch
>> > > > > and streaming: Nothing suspicious in log files found
>> > > > > * Verified Java version of uploaded binaries
>> > > > >
>> > > > > Thanks Yun Tang for taking care of it.
>> > > > >
>> > > > > On Thu, Nov 16, 2023 at 7:02 AM Rui Fan <1996fan...@gmail.com>
>> > wrote:
>> > > > >
>> > > > >> +1 (non-binding)
>> > > > >>
>> > > > >> - Verified signatures
>> > > > >> - Reviewed the flink-web PR, left a couple of comments
>> > > > >> - The source archives do not contain any binaries
>> > > > >> - Build the source with Maven 3 and java8 (Checked the license as
>> > > well)
>> > > > >> - bin/start-cluster.sh with java8, it works fine and no any
>> > unexpected
>> > > > LOG
>> > > > >> - Ran demo, it's fine:  bin/flink run
>> > > > >> examples/streaming/StateMachineExample.jar
>> > > > >>
>> > > > >> Best,
>> > > > >> Rui
>> > > > >>
>> > > > >> On Mon, Nov 13, 2023 at 4:04 PM Yun Tang 
>> wrote:
>> > > > >>
>> > > > >>> Hi everyone,
>> > > > >>>
>> > > > >>> Please review and vote on the release candidate #1 for the
>> version
>> > > > >> 1.17.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 2E0E1AB5D39D55E608071FB9F795C02A4D2482B3 [3],
>> > > > >>>
>> > > > >>> * all artifacts to be deployed to the Maven Central Repository
>> [4],
>> > > > >>>
>> > > > >>> * source code tag "release-1.17.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.
>> > > > >>>
>> > > > >>>
>> > > > >>> [1]
>> > > > >>>
>> > > > >>
>> > > >
>> > >
>> >
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353260
>> > > > >>>
>> > > > >>> [2]
>> https://dist.apache.org/repos/dist/dev/flink/flink-1.17.2-rc1/
>> > > > >>>
>> > > > >>> [3] https://dist.apache.org/repos/dist/release/flink/KEYS
>> > > > >>>
>> > > > >>> [4]
>> > > > >>>
>> > > >
>> > https://repository.apache.org/content/repositories/orgapacheflink-1669/
>> > > > >>>
>> > > > >>> [5]
>> > https://github.com/apache/flink/releases/tag/release-1.17.2-rc1
>> > > > >>>
>> > > > >>> [6] https://github.com/apache/flink-web/pull/696
>> > > > >>>
>> > > > >>> Thanks,
>> > > > >>> Release Manager
>> > > > >>>
>> > > > >>
>> > > >
>> > > >
>> > >
>> >
>>
>

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

[weijie guo]

+1 (binding)

- Verified signatures and hashsums
- Verified POM/NOTICE filess
- Built from sources.
- Reviewed the web PR.

Best regards,

Weijie


Yuxin Tan  于2023年11月24日周五 10:18写道：

> +1 (non-binding)
>
> - Verified signatures and hashsums
> - Verified there are no binaries in the source archive
> - Built Flink from sources
> - Reviewed the web PR
>
> Best,
> Yuxin
>
>
> Feng Jin  于2023年11月24日周五 02:20写道：
>
> > +1(non-binding)
> >
> > - verified signatures and hashsums
> > - Verified there are no binaries in the source archive
> > - Built Flink from sources
> > - Started local standalone cluster, submitted sql job using sql-client
> >
> > Best,
> > Feng
> >
> >
> > On Thu, Nov 23, 2023 at 11:08 PM Hang Ruan 
> wrote:
> >
> > > +1 (non-binding)
> > >
> > > - verified signatures
> > > - verified hashsums
> > > - Verified there are no binaries in the source archive
> > > - reviewed the web PR
> > > - built Flink from sources
> > >
> > > Best,
> > > Hang
> > >
> > > Jiabao Sun  于2023年11月23日周四 22:09写道：
> > >
> > > > Thanks for driving this release.
> > > >
> > > > +1(non-binding)
> > > >
> > > > - Checked the tag in git
> > > > - Verified signatures and hashsums
> > > > - Verified there are no binaries in the source archive
> > > > - Built Flink from sources
> > > >
> > > > Best,
> > > > Jiabao
> > > >
> > > >
> > > > > 2023年11月21日 20:46，Matthias Pohl 
> 写道：
> > > > >
> > > > > +1 (binding)
> > > > >
> > > > > * Downloaded artifacts
> > > > > * Built Flink from sources
> > > > > * Verified SHA512 checksums & GPG signatures
> > > > > * Compared checkout with provided sources
> > > > > * Verified pom file versions
> > > > > * Went over NOTICE/pom file changes without finding anything
> > suspicious
> > > > > * Deployed standalone session cluster and ran WordCount example in
> > > batch
> > > > > and streaming: Nothing suspicious in log files found
> > > > > * Verified Java version of uploaded binaries
> > > > >
> > > > > Thanks Yun Tang for taking care of it.
> > > > >
> > > > > On Thu, Nov 16, 2023 at 7:02 AM Rui Fan <1996fan...@gmail.com>
> > wrote:
> > > > >
> > > > >> +1 (non-binding)
> > > > >>
> > > > >> - Verified signatures
> > > > >> - Reviewed the flink-web PR, left a couple of comments
> > > > >> - The source archives do not contain any binaries
> > > > >> - Build the source with Maven 3 and java8 (Checked the license as
> > > well)
> > > > >> - bin/start-cluster.sh with java8, it works fine and no any
> > unexpected
> > > > LOG
> > > > >> - Ran demo, it's fine:  bin/flink run
> > > > >> examples/streaming/StateMachineExample.jar
> > > > >>
> > > > >> Best,
> > > > >> Rui
> > > > >>
> > > > >> On Mon, Nov 13, 2023 at 4:04 PM Yun Tang 
> wrote:
> > > > >>
> > > > >>> Hi everyone,
> > > > >>>
> > > > >>> Please review and vote on the release candidate #1 for the
> version
> > > > >> 1.17.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 2E0E1AB5D39D55E608071FB9F795C02A4D2482B3 [3],
> > > > >>>
> > > > >>> * all artifacts to be deployed to the Maven Central Repository
> [4],
> > > > >>>
> > > > >>> * source code tag "release-1.17.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.
> > > > >>>
> > > > >>>
> > > > >>> [1]
> > > > >>>
> > > > >>
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353260
> > > > >>>
> > > > >>> [2]
> https://dist.apache.org/repos/dist/dev/flink/flink-1.17.2-rc1/
> > > > >>>
> > > > >>> [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> > > > >>>
> > > > >>> [4]
> > > > >>>
> > > >
> > https://repository.apache.org/content/repositories/orgapacheflink-1669/
> > > > >>>
> > > > >>> [5]
> > https://github.com/apache/flink/releases/tag/release-1.17.2-rc1
> > > > >>>
> > > > >>> [6] https://github.com/apache/flink-web/pull/696
> > > > >>>
> > > > >>> Thanks,
> > > > >>> Release Manager
> > > > >>>
> > > > >>
> > > >
> > > >
> > >
> >
>

[jira] [Created] (FLINK-33636) Implement JdbcAutoScalerEventHandler

[Rui Fan (Jira)]

Rui Fan created FLINK-33636:
---

 Summary: Implement JdbcAutoScalerEventHandler
 Key: FLINK-33636
 URL: https://issues.apache.org/jira/browse/FLINK-33636
 Project: Flink
  Issue Type: Sub-task
  Components: Autoscaler
Reporter: Rui Fan
Assignee: Rui Fan






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

[jira] [Created] (FLINK-33635) ElasticSearch connector main branch can not compile

[Weijie Guo (Jira)]

Weijie Guo created FLINK-33635:
--

 Summary: ElasticSearch connector main branch can not compile
 Key: FLINK-33635
 URL: https://issues.apache.org/jira/browse/FLINK-33635
 Project: Flink
  Issue Type: Bug
  Components: Connectors / ElasticSearch
Reporter: Weijie Guo
Assignee: Weijie Guo


https://github.com/apache/flink-connector-elasticsearch/actions/runs/6976181890/job/18984287421



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

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

[Yuxin Tan]

+1 (non-binding)

- Verified signatures and hashsums
- Verified there are no binaries in the source archive
- Built Flink from sources
- Reviewed the web PR

Best,
Yuxin


Feng Jin  于2023年11月24日周五 02:20写道：

> +1(non-binding)
>
> - verified signatures and hashsums
> - Verified there are no binaries in the source archive
> - Built Flink from sources
> - Started local standalone cluster, submitted sql job using sql-client
>
> Best,
> Feng
>
>
> On Thu, Nov 23, 2023 at 11:08 PM Hang Ruan  wrote:
>
> > +1 (non-binding)
> >
> > - verified signatures
> > - verified hashsums
> > - Verified there are no binaries in the source archive
> > - reviewed the web PR
> > - built Flink from sources
> >
> > Best,
> > Hang
> >
> > Jiabao Sun  于2023年11月23日周四 22:09写道：
> >
> > > Thanks for driving this release.
> > >
> > > +1(non-binding)
> > >
> > > - Checked the tag in git
> > > - Verified signatures and hashsums
> > > - Verified there are no binaries in the source archive
> > > - Built Flink from sources
> > >
> > > Best,
> > > Jiabao
> > >
> > >
> > > > 2023年11月21日 20:46，Matthias Pohl  写道：
> > > >
> > > > +1 (binding)
> > > >
> > > > * Downloaded artifacts
> > > > * Built Flink from sources
> > > > * Verified SHA512 checksums & GPG signatures
> > > > * Compared checkout with provided sources
> > > > * Verified pom file versions
> > > > * Went over NOTICE/pom file changes without finding anything
> suspicious
> > > > * Deployed standalone session cluster and ran WordCount example in
> > batch
> > > > and streaming: Nothing suspicious in log files found
> > > > * Verified Java version of uploaded binaries
> > > >
> > > > Thanks Yun Tang for taking care of it.
> > > >
> > > > On Thu, Nov 16, 2023 at 7:02 AM Rui Fan <1996fan...@gmail.com>
> wrote:
> > > >
> > > >> +1 (non-binding)
> > > >>
> > > >> - Verified signatures
> > > >> - Reviewed the flink-web PR, left a couple of comments
> > > >> - The source archives do not contain any binaries
> > > >> - Build the source with Maven 3 and java8 (Checked the license as
> > well)
> > > >> - bin/start-cluster.sh with java8, it works fine and no any
> unexpected
> > > LOG
> > > >> - Ran demo, it's fine:  bin/flink run
> > > >> examples/streaming/StateMachineExample.jar
> > > >>
> > > >> Best,
> > > >> Rui
> > > >>
> > > >> On Mon, Nov 13, 2023 at 4:04 PM Yun Tang  wrote:
> > > >>
> > > >>> Hi everyone,
> > > >>>
> > > >>> Please review and vote on the release candidate #1 for the version
> > > >> 1.17.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 2E0E1AB5D39D55E608071FB9F795C02A4D2482B3 [3],
> > > >>>
> > > >>> * all artifacts to be deployed to the Maven Central Repository [4],
> > > >>>
> > > >>> * source code tag "release-1.17.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.
> > > >>>
> > > >>>
> > > >>> [1]
> > > >>>
> > > >>
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353260
> > > >>>
> > > >>> [2] https://dist.apache.org/repos/dist/dev/flink/flink-1.17.2-rc1/
> > > >>>
> > > >>> [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> > > >>>
> > > >>> [4]
> > > >>>
> > >
> https://repository.apache.org/content/repositories/orgapacheflink-1669/
> > > >>>
> > > >>> [5]
> https://github.com/apache/flink/releases/tag/release-1.17.2-rc1
> > > >>>
> > > >>> [6] https://github.com/apache/flink-web/pull/696
> > > >>>
> > > >>> Thanks,
> > > >>> Release Manager
> > > >>>
> > > >>
> > >
> > >
> >
>

Re: [VOTE] Release flink-connector-opensearch v1.1.0, release candidate #1

[Tzu-Li (Gordon) Tai]

Hi Danny,

Thanks for starting a RC for this.

>From the looks of the staged POMs for 1.1.0-1.18, the flink versions for
Flink dependencies still point to 1.17.1.

My understanding is that this is fine, as those provided scope
dependencies (e.g. flink-streaming-java) will have their versions
overwritten by the user POM if they do intend to compile their jobs against
Flink 1.18.x.
Can you clarify if this is the correct understanding of how we intend the
externalized connector artifacts to be published? Related discussion on [1].

Thanks,
Gordon

[1] https://lists.apache.org/thread/x1pyrrrq7o1wv1lcdovhzpo4qhd4tvb4

On Thu, Nov 23, 2023 at 3:14 PM Sergey Nuyanzin  wrote:

> +1 (non-binding)
>
> - downloaded artifacts
> - built from source
> - verified checksums and signatures
> - reviewed web pr
>
>
> On Mon, Nov 6, 2023 at 5:31 PM Ryan Skraba 
> wrote:
>
> > Hello! +1 (non-binding) Thanks for the release!
> >
> > I've validated the source for the RC1:
> > * flink-connector-opensearch-1.1.0-src.tgz at r64995
> > * The sha512 checksum is OK.
> > * The source file is signed correctly.
> > * The signature 0F79F2AFB2351BC29678544591F9C1EC125FD8DB is found in the
> > KEYS file, and on https://keyserver.ubuntu.com/
> > * The source file is consistent with the GitHub tag v1.1.0-rc1, which
> > corresponds to commit 0f659cc65131c9ff7c8c35eb91f5189e80414ea1
> > - The files explicitly excluded by create_pristine_sources (such as
> > .gitignore and the submodule tools/releasing/shared) are not present.
> > * Has a LICENSE file and a NOTICE file
> > * Does not contain any compiled binaries.
> >
> > * The sources can be compiled and unit tests pass with flink.version
> 1.17.1
> > and flink.version 1.18.0
> >
> > * Nexus has three staged artifact ids for 1.1.0-1.17 and 1.1.0-1.18
> > - flink-connector-opensearch (.jar, -javadoc.jar, -sources.jar,
> > -tests.jar and .pom)
> > - flink-sql-connector-opensearch (.jar, -sources.jar and .pom)
> > - flink-connector-gcp-pubsub-parent (only .pom)
> >
> > All my best, Ryan
> >
> > On Fri, Nov 3, 2023 at 10:29 AM Danny Cranmer 
> > wrote:
> > >
> > > Hi everyone,
> > >
> > > Please review and vote on the release candidate #1 for the version
> 1.1.0
> > of
> > > flink-connector-opensearch, 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 to be deployed to dist.apache.org
> > [2],
> > > which are signed with the key with fingerprint
> > > 0F79F2AFB2351BC29678544591F9C1EC125FD8DB [3],
> > > * all artifacts to be deployed to the Maven Central Repository [4],
> > > * source code tag v1.1.0-rc1 [5],
> > > * website pull request listing the new release [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,
> > > Danny
> > >
> > > [1]
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353141
> > > [2]
> > >
> >
> https://dist.apache.org/repos/dist/dev/flink/flink-connector-opensearch-1.1.0-rc1/
> > > [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> > > [4]
> > https://repository.apache.org/content/repositories/orgapacheflink-1666/
> > > [5]
> https://github.com/apache/flink-connector-opensearch/tree/v1.1.0-rc1
> > > [6] https://github.com/apache/flink-web/pull/694
> >
>
>
> --
> Best regards,
> Sergey
>

Re: [VOTE] Release flink-connector-opensearch v1.1.0, release candidate #1

[Sergey Nuyanzin]

+1 (non-binding)

- downloaded artifacts
- built from source
- verified checksums and signatures
- reviewed web pr


On Mon, Nov 6, 2023 at 5:31 PM Ryan Skraba 
wrote:

> Hello! +1 (non-binding) Thanks for the release!
>
> I've validated the source for the RC1:
> * flink-connector-opensearch-1.1.0-src.tgz at r64995
> * The sha512 checksum is OK.
> * The source file is signed correctly.
> * The signature 0F79F2AFB2351BC29678544591F9C1EC125FD8DB is found in the
> KEYS file, and on https://keyserver.ubuntu.com/
> * The source file is consistent with the GitHub tag v1.1.0-rc1, which
> corresponds to commit 0f659cc65131c9ff7c8c35eb91f5189e80414ea1
> - The files explicitly excluded by create_pristine_sources (such as
> .gitignore and the submodule tools/releasing/shared) are not present.
> * Has a LICENSE file and a NOTICE file
> * Does not contain any compiled binaries.
>
> * The sources can be compiled and unit tests pass with flink.version 1.17.1
> and flink.version 1.18.0
>
> * Nexus has three staged artifact ids for 1.1.0-1.17 and 1.1.0-1.18
> - flink-connector-opensearch (.jar, -javadoc.jar, -sources.jar,
> -tests.jar and .pom)
> - flink-sql-connector-opensearch (.jar, -sources.jar and .pom)
> - flink-connector-gcp-pubsub-parent (only .pom)
>
> All my best, Ryan
>
> On Fri, Nov 3, 2023 at 10:29 AM Danny Cranmer 
> wrote:
> >
> > Hi everyone,
> >
> > Please review and vote on the release candidate #1 for the version 1.1.0
> of
> > flink-connector-opensearch, 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 to be deployed to dist.apache.org
> [2],
> > which are signed with the key with fingerprint
> > 0F79F2AFB2351BC29678544591F9C1EC125FD8DB [3],
> > * all artifacts to be deployed to the Maven Central Repository [4],
> > * source code tag v1.1.0-rc1 [5],
> > * website pull request listing the new release [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,
> > Danny
> >
> > [1]
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353141
> > [2]
> >
> https://dist.apache.org/repos/dist/dev/flink/flink-connector-opensearch-1.1.0-rc1/
> > [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> > [4]
> https://repository.apache.org/content/repositories/orgapacheflink-1666/
> > [5] https://github.com/apache/flink-connector-opensearch/tree/v1.1.0-rc1
> > [6] https://github.com/apache/flink-web/pull/694
>


-- 
Best regards,
Sergey

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

[Feng Jin]

+1(non-binding)

- verified signatures and hashsums
- Verified there are no binaries in the source archive
- Built Flink from sources
- Started local standalone cluster, submitted sql job using sql-client

Best,
Feng

On Thu, Nov 23, 2023 at 11:00 PM Hang Ruan  wrote:

> +1 (non-binding)
>
> - verified signatures
> - verified hashsums
> - Verified there are no binaries in the source archive
> - reviewed the Release Note
> - reviewed the web PR
>
> Best,
> Hang
>
> Jiabao Sun  于2023年11月23日周四 22:15写道：
>
> > Thanks for driving this release.
> >
> > +1 (non-binding)
> >
> > - Checked the tag in git
> > - Verified signatures and hashsums
> > - Verified there are no binaries in the source archive
> > - Built Flink from sources
> >
> > Best,
> > Jiabao
> >
> > > 2023年11月23日 21:55，Sergey Nuyanzin  写道：
> > >
> > > +1 (non-binding)
> > >
> > > - Downloaded artifacts
> > > - Built Flink from sources
> > > - Verified checksums & signatures
> > > - Verified pom/NOTICE files
> > > - reviewed the web PR
> > >
> > > On Thu, Nov 23, 2023 at 1:28 PM Leonard Xu  wrote:
> > >
> > >> +1 (binding)
> > >>
> > >> - verified signatures
> > >> - verified hashsums
> > >> - checked that all POM files point to the same version 1.16.3
> > >> - started SQL Client, used MySQL CDC connector to read changelog from
> > >> database , the result is expected
> > >> - reviewed the web PR, left minor comment
> > >>
> > >> Best,
> > >> Leonard
> > >>
> > >>> 2023年11月21日 下午8:56，Matthias Pohl 
> 写道：
> > >>>
> > >>> +1 (binding)
> > >>>
> > >>> * Downloaded artifacts
> > >>> * Built Flink from sources
> > >>> * Verified SHA512 checksums & GPG signatures
> > >>> * Compared checkout with provided sources
> > >>> * Verified pom file versions
> > >>> * Went over NOTICE/pom file changes without finding anything
> suspicious
> > >>> * Deployed standalone session cluster and ran WordCount example in
> > batch
> > >>> and streaming: Nothing suspicious in log files found
> > >>> * Verified Java version of uploaded binaries
> > >>>
> > >>> Thanks for wrapping 1.16 up. :)
> > >>>
> > >>> On Tue, Nov 21, 2023 at 4:55 AM Rui Fan <1996fan...@gmail.com>
> wrote:
> > >>>
> >  +1 (non-binding)
> > 
> >  Verified based on this wiki[1].
> > 
> >  - Verified signatures and sha512
> >  - The source archives do not contain any binaries
> >  - Build the source with Maven 3 and java8 (Checked the license as
> > well)
> >  - bin/start-cluster.sh with java8, it works fine and no any
> unexpected
> > >> LOG
> >  - Ran demo, it's fine:  bin/flink run
> >  examples/streaming/StateMachineExample.jar
> > 
> >  [1]
> > 
> > >>
> >
> https://cwiki.apache.org/confluence/display/FLINK/Verifying+a+Flink+Release
> > 
> >  Best,
> >  Rui
> > 
> >  On Fri, Nov 17, 2023 at 11:52 AM Yun Tang  wrote:
> > 
> > > +1 (non-binding)
> > >
> > >
> > > *   Verified signatures
> > > *   Build from source code, and it looks good
> > > *   Verified that jar packages are built with maven-3.2.5 and JDK8
> > > *   Reviewed the flink-web PR
> > > *   Start a local standalone cluster and submit examples
> > >
> > > Best
> > > Yun Tang
> > > 
> > > From: Rui Fan <1996fan...@gmail.com>
> > > Sent: Monday, November 13, 2023 18:20
> > > To: dev 
> > > Subject: [VOTE] Release 1.16.3, release candidate #1
> > >
> > > Hi everyone,
> > >
> > > Please review and vote on the release candidate #1 for the version
> >  1.16.3,
> > >
> > > 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 B2D64016B940A7E0B9B72E0D7D0528B28037D8BC [3],
> > >
> > > * all artifacts to be deployed to the Maven Central Repository [4],
> > >
> > > * source code tag "release-1.16.3-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.
> > >
> > >
> > > [1]
> > >
> > >
> > 
> > >>
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353259
> > >
> > > [2] https://dist.apache.org/repos/dist/dev/flink/flink-1.16.3-rc1/
> > >
> > > [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> > >
> > > [4]
> > >
> > >>
> 

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

[Feng Jin]

+1(non-binding)

- verified signatures and hashsums
- Verified there are no binaries in the source archive
- Built Flink from sources
- Started local standalone cluster, submitted sql job using sql-client

Best,
Feng


On Thu, Nov 23, 2023 at 11:08 PM Hang Ruan  wrote:

> +1 (non-binding)
>
> - verified signatures
> - verified hashsums
> - Verified there are no binaries in the source archive
> - reviewed the web PR
> - built Flink from sources
>
> Best,
> Hang
>
> Jiabao Sun  于2023年11月23日周四 22:09写道：
>
> > Thanks for driving this release.
> >
> > +1(non-binding)
> >
> > - Checked the tag in git
> > - Verified signatures and hashsums
> > - Verified there are no binaries in the source archive
> > - Built Flink from sources
> >
> > Best,
> > Jiabao
> >
> >
> > > 2023年11月21日 20:46，Matthias Pohl  写道：
> > >
> > > +1 (binding)
> > >
> > > * Downloaded artifacts
> > > * Built Flink from sources
> > > * Verified SHA512 checksums & GPG signatures
> > > * Compared checkout with provided sources
> > > * Verified pom file versions
> > > * Went over NOTICE/pom file changes without finding anything suspicious
> > > * Deployed standalone session cluster and ran WordCount example in
> batch
> > > and streaming: Nothing suspicious in log files found
> > > * Verified Java version of uploaded binaries
> > >
> > > Thanks Yun Tang for taking care of it.
> > >
> > > On Thu, Nov 16, 2023 at 7:02 AM Rui Fan <1996fan...@gmail.com> wrote:
> > >
> > >> +1 (non-binding)
> > >>
> > >> - Verified signatures
> > >> - Reviewed the flink-web PR, left a couple of comments
> > >> - The source archives do not contain any binaries
> > >> - Build the source with Maven 3 and java8 (Checked the license as
> well)
> > >> - bin/start-cluster.sh with java8, it works fine and no any unexpected
> > LOG
> > >> - Ran demo, it's fine:  bin/flink run
> > >> examples/streaming/StateMachineExample.jar
> > >>
> > >> Best,
> > >> Rui
> > >>
> > >> On Mon, Nov 13, 2023 at 4:04 PM Yun Tang  wrote:
> > >>
> > >>> Hi everyone,
> > >>>
> > >>> Please review and vote on the release candidate #1 for the version
> > >> 1.17.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 2E0E1AB5D39D55E608071FB9F795C02A4D2482B3 [3],
> > >>>
> > >>> * all artifacts to be deployed to the Maven Central Repository [4],
> > >>>
> > >>> * source code tag "release-1.17.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.
> > >>>
> > >>>
> > >>> [1]
> > >>>
> > >>
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353260
> > >>>
> > >>> [2] https://dist.apache.org/repos/dist/dev/flink/flink-1.17.2-rc1/
> > >>>
> > >>> [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> > >>>
> > >>> [4]
> > >>>
> > https://repository.apache.org/content/repositories/orgapacheflink-1669/
> > >>>
> > >>> [5] https://github.com/apache/flink/releases/tag/release-1.17.2-rc1
> > >>>
> > >>> [6] https://github.com/apache/flink-web/pull/696
> > >>>
> > >>> Thanks,
> > >>> Release Manager
> > >>>
> > >>
> >
> >
>

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

[Hang Ruan]

+1 (non-binding)

- verified signatures
- verified hashsums
- Verified there are no binaries in the source archive
- reviewed the web PR
- built Flink from sources

Best,
Hang

Jiabao Sun  于2023年11月23日周四 22:09写道：

> Thanks for driving this release.
>
> +1(non-binding)
>
> - Checked the tag in git
> - Verified signatures and hashsums
> - Verified there are no binaries in the source archive
> - Built Flink from sources
>
> Best,
> Jiabao
>
>
> > 2023年11月21日 20:46，Matthias Pohl  写道：
> >
> > +1 (binding)
> >
> > * Downloaded artifacts
> > * Built Flink from sources
> > * Verified SHA512 checksums & GPG signatures
> > * Compared checkout with provided sources
> > * Verified pom file versions
> > * Went over NOTICE/pom file changes without finding anything suspicious
> > * Deployed standalone session cluster and ran WordCount example in batch
> > and streaming: Nothing suspicious in log files found
> > * Verified Java version of uploaded binaries
> >
> > Thanks Yun Tang for taking care of it.
> >
> > On Thu, Nov 16, 2023 at 7:02 AM Rui Fan <1996fan...@gmail.com> wrote:
> >
> >> +1 (non-binding)
> >>
> >> - Verified signatures
> >> - Reviewed the flink-web PR, left a couple of comments
> >> - The source archives do not contain any binaries
> >> - Build the source with Maven 3 and java8 (Checked the license as well)
> >> - bin/start-cluster.sh with java8, it works fine and no any unexpected
> LOG
> >> - Ran demo, it's fine:  bin/flink run
> >> examples/streaming/StateMachineExample.jar
> >>
> >> Best,
> >> Rui
> >>
> >> On Mon, Nov 13, 2023 at 4:04 PM Yun Tang  wrote:
> >>
> >>> Hi everyone,
> >>>
> >>> Please review and vote on the release candidate #1 for the version
> >> 1.17.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 2E0E1AB5D39D55E608071FB9F795C02A4D2482B3 [3],
> >>>
> >>> * all artifacts to be deployed to the Maven Central Repository [4],
> >>>
> >>> * source code tag "release-1.17.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.
> >>>
> >>>
> >>> [1]
> >>>
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353260
> >>>
> >>> [2] https://dist.apache.org/repos/dist/dev/flink/flink-1.17.2-rc1/
> >>>
> >>> [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> >>>
> >>> [4]
> >>>
> https://repository.apache.org/content/repositories/orgapacheflink-1669/
> >>>
> >>> [5] https://github.com/apache/flink/releases/tag/release-1.17.2-rc1
> >>>
> >>> [6] https://github.com/apache/flink-web/pull/696
> >>>
> >>> Thanks,
> >>> Release Manager
> >>>
> >>
>
>

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

[Hang Ruan]

+1 (non-binding)

- verified signatures
- verified hashsums
- Verified there are no binaries in the source archive
- reviewed the Release Note
- reviewed the web PR

Best,
Hang

Jiabao Sun  于2023年11月23日周四 22:15写道：

> Thanks for driving this release.
>
> +1 (non-binding)
>
> - Checked the tag in git
> - Verified signatures and hashsums
> - Verified there are no binaries in the source archive
> - Built Flink from sources
>
> Best,
> Jiabao
>
> > 2023年11月23日 21:55，Sergey Nuyanzin  写道：
> >
> > +1 (non-binding)
> >
> > - Downloaded artifacts
> > - Built Flink from sources
> > - Verified checksums & signatures
> > - Verified pom/NOTICE files
> > - reviewed the web PR
> >
> > On Thu, Nov 23, 2023 at 1:28 PM Leonard Xu  wrote:
> >
> >> +1 (binding)
> >>
> >> - verified signatures
> >> - verified hashsums
> >> - checked that all POM files point to the same version 1.16.3
> >> - started SQL Client, used MySQL CDC connector to read changelog from
> >> database , the result is expected
> >> - reviewed the web PR, left minor comment
> >>
> >> Best,
> >> Leonard
> >>
> >>> 2023年11月21日 下午8:56，Matthias Pohl  写道：
> >>>
> >>> +1 (binding)
> >>>
> >>> * Downloaded artifacts
> >>> * Built Flink from sources
> >>> * Verified SHA512 checksums & GPG signatures
> >>> * Compared checkout with provided sources
> >>> * Verified pom file versions
> >>> * Went over NOTICE/pom file changes without finding anything suspicious
> >>> * Deployed standalone session cluster and ran WordCount example in
> batch
> >>> and streaming: Nothing suspicious in log files found
> >>> * Verified Java version of uploaded binaries
> >>>
> >>> Thanks for wrapping 1.16 up. :)
> >>>
> >>> On Tue, Nov 21, 2023 at 4:55 AM Rui Fan <1996fan...@gmail.com> wrote:
> >>>
>  +1 (non-binding)
> 
>  Verified based on this wiki[1].
> 
>  - Verified signatures and sha512
>  - The source archives do not contain any binaries
>  - Build the source with Maven 3 and java8 (Checked the license as
> well)
>  - bin/start-cluster.sh with java8, it works fine and no any unexpected
> >> LOG
>  - Ran demo, it's fine:  bin/flink run
>  examples/streaming/StateMachineExample.jar
> 
>  [1]
> 
> >>
> https://cwiki.apache.org/confluence/display/FLINK/Verifying+a+Flink+Release
> 
>  Best,
>  Rui
> 
>  On Fri, Nov 17, 2023 at 11:52 AM Yun Tang  wrote:
> 
> > +1 (non-binding)
> >
> >
> > *   Verified signatures
> > *   Build from source code, and it looks good
> > *   Verified that jar packages are built with maven-3.2.5 and JDK8
> > *   Reviewed the flink-web PR
> > *   Start a local standalone cluster and submit examples
> >
> > Best
> > Yun Tang
> > 
> > From: Rui Fan <1996fan...@gmail.com>
> > Sent: Monday, November 13, 2023 18:20
> > To: dev 
> > Subject: [VOTE] Release 1.16.3, release candidate #1
> >
> > Hi everyone,
> >
> > Please review and vote on the release candidate #1 for the version
>  1.16.3,
> >
> > 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 B2D64016B940A7E0B9B72E0D7D0528B28037D8BC [3],
> >
> > * all artifacts to be deployed to the Maven Central Repository [4],
> >
> > * source code tag "release-1.16.3-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.
> >
> >
> > [1]
> >
> >
> 
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353259
> >
> > [2] https://dist.apache.org/repos/dist/dev/flink/flink-1.16.3-rc1/
> >
> > [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> >
> > [4]
> >
> >> https://repository.apache.org/content/repositories/orgapacheflink-1670/
> >
> > [5] https://github.com/apache/flink/releases/tag/release-1.16.3-rc1
> >
> > [6] https://github.com/apache/flink-web/pull/698
> >
> > Thanks,
> > Release Manager
> >
> 
> >>
> >>
> >
> > --
> > Best regards,
> > Sergey
>
>

[jira] [Created] (FLINK-33634) Add Conditions to Flink CRD's Status field

[Tony Garrard (Jira)]

Tony Garrard created FLINK-33634:


 Summary: Add Conditions to Flink CRD's Status field
 Key: FLINK-33634
 URL: https://issues.apache.org/jira/browse/FLINK-33634
 Project: Flink
  Issue Type: Improvement
  Components: Kubernetes Operator
Affects Versions: kubernetes-operator-1.7.0
Reporter: Tony Garrard


>From 
>[https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#typical-status-properties]
> it is considered best practice to provide Conditions in the Status of CRD's. 
>Some tooling even expects there to be a Conditions field in the status of a 
>CR. This issue to to propose adding a Conditions field to the CR status

e.g.
status:
    conditions:
     - lastTransitionTime: '2023-11-23T12:38:51Z'
       status: 'True'
       type: Ready



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

[jira] [Created] (FLINK-33633) Automatic creation of RBAC for instances of Flink Deployments

[Tony Garrard (Jira)]

Tony Garrard created FLINK-33633:


 Summary: Automatic creation of RBAC for instances of Flink 
Deployments
 Key: FLINK-33633
 URL: https://issues.apache.org/jira/browse/FLINK-33633
 Project: Flink
  Issue Type: Improvement
  Components: Kubernetes Operator
Affects Versions: kubernetes-operator-1.7.0
Reporter: Tony Garrard


Currently users have to manually create RBAC e.g. the flink service account. 
When operator is watching all namespaces; creation of a FlinkDeployment in a 
specific namespace may fail if the kube admin has failed to create the required 
RBAC. To improve usability the operator could be coded to automatically create 
these rbac resources in the instance namespace if not present



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

[jira] [Created] (FLINK-33632) Add custom mutator plugin

[Tony Garrard (Jira)]

Tony Garrard created FLINK-33632:


 Summary: Add custom mutator plugin
 Key: FLINK-33632
 URL: https://issues.apache.org/jira/browse/FLINK-33632
 Project: Flink
  Issue Type: Improvement
  Components: Kubernetes Operator
Affects Versions: kubernetes-operator-1.7.0
Reporter: Tony Garrard


Currently users have the ability to provide custom validators to the operator. 
It would be great if we followed the same pattern to provide custom mutators



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

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

[Jiabao Sun]

Thanks for driving this release.

+1 (non-binding)

- Checked the tag in git
- Verified signatures and hashsums
- Verified there are no binaries in the source archive
- Built Flink from sources

Best,
Jiabao

> 2023年11月23日 21:55，Sergey Nuyanzin  写道：
> 
> +1 (non-binding)
> 
> - Downloaded artifacts
> - Built Flink from sources
> - Verified checksums & signatures
> - Verified pom/NOTICE files
> - reviewed the web PR
> 
> On Thu, Nov 23, 2023 at 1:28 PM Leonard Xu  wrote:
> 
>> +1 (binding)
>> 
>> - verified signatures
>> - verified hashsums
>> - checked that all POM files point to the same version 1.16.3
>> - started SQL Client, used MySQL CDC connector to read changelog from
>> database , the result is expected
>> - reviewed the web PR, left minor comment
>> 
>> Best,
>> Leonard
>> 
>>> 2023年11月21日 下午8:56，Matthias Pohl  写道：
>>> 
>>> +1 (binding)
>>> 
>>> * Downloaded artifacts
>>> * Built Flink from sources
>>> * Verified SHA512 checksums & GPG signatures
>>> * Compared checkout with provided sources
>>> * Verified pom file versions
>>> * Went over NOTICE/pom file changes without finding anything suspicious
>>> * Deployed standalone session cluster and ran WordCount example in batch
>>> and streaming: Nothing suspicious in log files found
>>> * Verified Java version of uploaded binaries
>>> 
>>> Thanks for wrapping 1.16 up. :)
>>> 
>>> On Tue, Nov 21, 2023 at 4:55 AM Rui Fan <1996fan...@gmail.com> wrote:
>>> 
 +1 (non-binding)
 
 Verified based on this wiki[1].
 
 - Verified signatures and sha512
 - The source archives do not contain any binaries
 - Build the source with Maven 3 and java8 (Checked the license as well)
 - bin/start-cluster.sh with java8, it works fine and no any unexpected
>> LOG
 - Ran demo, it's fine:  bin/flink run
 examples/streaming/StateMachineExample.jar
 
 [1]
 
>> https://cwiki.apache.org/confluence/display/FLINK/Verifying+a+Flink+Release
 
 Best,
 Rui
 
 On Fri, Nov 17, 2023 at 11:52 AM Yun Tang  wrote:
 
> +1 (non-binding)
> 
> 
> *   Verified signatures
> *   Build from source code, and it looks good
> *   Verified that jar packages are built with maven-3.2.5 and JDK8
> *   Reviewed the flink-web PR
> *   Start a local standalone cluster and submit examples
> 
> Best
> Yun Tang
> 
> From: Rui Fan <1996fan...@gmail.com>
> Sent: Monday, November 13, 2023 18:20
> To: dev 
> Subject: [VOTE] Release 1.16.3, release candidate #1
> 
> Hi everyone,
> 
> Please review and vote on the release candidate #1 for the version
 1.16.3,
> 
> 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 B2D64016B940A7E0B9B72E0D7D0528B28037D8BC [3],
> 
> * all artifacts to be deployed to the Maven Central Repository [4],
> 
> * source code tag "release-1.16.3-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.
> 
> 
> [1]
> 
> 
 
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353259
> 
> [2] https://dist.apache.org/repos/dist/dev/flink/flink-1.16.3-rc1/
> 
> [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> 
> [4]
> 
>> https://repository.apache.org/content/repositories/orgapacheflink-1670/
> 
> [5] https://github.com/apache/flink/releases/tag/release-1.16.3-rc1
> 
> [6] https://github.com/apache/flink-web/pull/698
> 
> Thanks,
> Release Manager
> 
 
>> 
>> 
> 
> -- 
> Best regards,
> Sergey

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

[Jiabao Sun]

Thanks for driving this release.

+1(non-binding)

- Checked the tag in git
- Verified signatures and hashsums
- Verified there are no binaries in the source archive
- Built Flink from sources

Best,
Jiabao


> 2023年11月21日 20:46，Matthias Pohl  写道：
> 
> +1 (binding)
> 
> * Downloaded artifacts
> * Built Flink from sources
> * Verified SHA512 checksums & GPG signatures
> * Compared checkout with provided sources
> * Verified pom file versions
> * Went over NOTICE/pom file changes without finding anything suspicious
> * Deployed standalone session cluster and ran WordCount example in batch
> and streaming: Nothing suspicious in log files found
> * Verified Java version of uploaded binaries
> 
> Thanks Yun Tang for taking care of it.
> 
> On Thu, Nov 16, 2023 at 7:02 AM Rui Fan <1996fan...@gmail.com> wrote:
> 
>> +1 (non-binding)
>> 
>> - Verified signatures
>> - Reviewed the flink-web PR, left a couple of comments
>> - The source archives do not contain any binaries
>> - Build the source with Maven 3 and java8 (Checked the license as well)
>> - bin/start-cluster.sh with java8, it works fine and no any unexpected LOG
>> - Ran demo, it's fine:  bin/flink run
>> examples/streaming/StateMachineExample.jar
>> 
>> Best,
>> Rui
>> 
>> On Mon, Nov 13, 2023 at 4:04 PM Yun Tang  wrote:
>> 
>>> Hi everyone,
>>> 
>>> Please review and vote on the release candidate #1 for the version
>> 1.17.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 2E0E1AB5D39D55E608071FB9F795C02A4D2482B3 [3],
>>> 
>>> * all artifacts to be deployed to the Maven Central Repository [4],
>>> 
>>> * source code tag "release-1.17.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.
>>> 
>>> 
>>> [1]
>>> 
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353260
>>> 
>>> [2] https://dist.apache.org/repos/dist/dev/flink/flink-1.17.2-rc1/
>>> 
>>> [3] https://dist.apache.org/repos/dist/release/flink/KEYS
>>> 
>>> [4]
>>> https://repository.apache.org/content/repositories/orgapacheflink-1669/
>>> 
>>> [5] https://github.com/apache/flink/releases/tag/release-1.17.2-rc1
>>> 
>>> [6] https://github.com/apache/flink-web/pull/696
>>> 
>>> Thanks,
>>> Release Manager
>>> 
>> 

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

[Sergey Nuyanzin]

+1 (non-binding)

- Downloaded artifacts
- Built Flink from sources
- Verified checksums & signatures
- Verified pom/NOTICE files
- reviewed the web PR

On Thu, Nov 23, 2023 at 1:28 PM Leonard Xu  wrote:

> +1 (binding)
>
> - verified signatures
> - verified hashsums
> - checked that all POM files point to the same version 1.16.3
> - started SQL Client, used MySQL CDC connector to read changelog from
> database , the result is expected
> - reviewed the web PR, left minor comment
>
> Best,
> Leonard
>
> > 2023年11月21日 下午8:56，Matthias Pohl  写道：
> >
> > +1 (binding)
> >
> > * Downloaded artifacts
> > * Built Flink from sources
> > * Verified SHA512 checksums & GPG signatures
> > * Compared checkout with provided sources
> > * Verified pom file versions
> > * Went over NOTICE/pom file changes without finding anything suspicious
> > * Deployed standalone session cluster and ran WordCount example in batch
> > and streaming: Nothing suspicious in log files found
> > * Verified Java version of uploaded binaries
> >
> > Thanks for wrapping 1.16 up. :)
> >
> > On Tue, Nov 21, 2023 at 4:55 AM Rui Fan <1996fan...@gmail.com> wrote:
> >
> >> +1 (non-binding)
> >>
> >> Verified based on this wiki[1].
> >>
> >> - Verified signatures and sha512
> >> - The source archives do not contain any binaries
> >> - Build the source with Maven 3 and java8 (Checked the license as well)
> >> - bin/start-cluster.sh with java8, it works fine and no any unexpected
> LOG
> >> - Ran demo, it's fine:  bin/flink run
> >> examples/streaming/StateMachineExample.jar
> >>
> >> [1]
> >>
> https://cwiki.apache.org/confluence/display/FLINK/Verifying+a+Flink+Release
> >>
> >> Best,
> >> Rui
> >>
> >> On Fri, Nov 17, 2023 at 11:52 AM Yun Tang  wrote:
> >>
> >>> +1 (non-binding)
> >>>
> >>>
> >>>  *   Verified signatures
> >>>  *   Build from source code, and it looks good
> >>>  *   Verified that jar packages are built with maven-3.2.5 and JDK8
> >>>  *   Reviewed the flink-web PR
> >>>  *   Start a local standalone cluster and submit examples
> >>>
> >>> Best
> >>> Yun Tang
> >>> 
> >>> From: Rui Fan <1996fan...@gmail.com>
> >>> Sent: Monday, November 13, 2023 18:20
> >>> To: dev 
> >>> Subject: [VOTE] Release 1.16.3, release candidate #1
> >>>
> >>> Hi everyone,
> >>>
> >>> Please review and vote on the release candidate #1 for the version
> >> 1.16.3,
> >>>
> >>> 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 B2D64016B940A7E0B9B72E0D7D0528B28037D8BC [3],
> >>>
> >>> * all artifacts to be deployed to the Maven Central Repository [4],
> >>>
> >>> * source code tag "release-1.16.3-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.
> >>>
> >>>
> >>> [1]
> >>>
> >>>
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353259
> >>>
> >>> [2] https://dist.apache.org/repos/dist/dev/flink/flink-1.16.3-rc1/
> >>>
> >>> [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> >>>
> >>> [4]
> >>>
> https://repository.apache.org/content/repositories/orgapacheflink-1670/
> >>>
> >>> [5] https://github.com/apache/flink/releases/tag/release-1.16.3-rc1
> >>>
> >>> [6] https://github.com/apache/flink-web/pull/698
> >>>
> >>> Thanks,
> >>> Release Manager
> >>>
> >>
>
>

-- 
Best regards,
Sergey

Discussion: [FLINK-33609] Take into account the resource limit specified in the pod template

[Surendra Singh Lilhore]

Hello everyone,

I've encountered an issue while using the flink open source
kubernetes operator for Flink deployment. Despite setting resource limits
in the pod template, it appears that these limits are not considered during
TaskManager (TM) pod deployment. Upon code investigation, it seems the
limits are being overridden by the default limit factor in
KubernetesUtils#getResourceRequirements()

.

The current behavior of Flink only considers the limit from the default
factor, neglecting pod template resource limits. I propose Flink should
incorporate both the limit factor and pod template resource limits, taking
the maximum value.

I've raised the issue and submitted a pull request:  FLINK-33609


During the review process, a valid concern was raised regarding the
proposed changes. The suggestion is to initiate a quick discussion, as this
modification will significantly alter the resource handling logic. It's
emphasized that maintaining consistency in the logic for both resource
requests and limits is crucial, rather than applying changes to only one of
them.

I would appreciate any feedback on this.

Thank you for your time and contributions to the Flink project.

Thank you,
Surendra

[jira] [Created] (FLINK-33631) Remove HA ConfigMap label setup

[Matthias Pohl (Jira)]

Matthias Pohl created FLINK-33631:
-

 Summary: Remove HA ConfigMap label setup
 Key: FLINK-33631
 URL: https://issues.apache.org/jira/browse/FLINK-33631
 Project: Flink
  Issue Type: Improvement
  Components: Deployment / Kubernetes
Reporter: Matthias Pohl
 Fix For: 2.0.0


FLINK-33598 removed the ConfigMap labels for identifying HA ConfigMaps. 
Instead, the single ConfigMap is addressed by its name to reduce k8s API 
requests. The labeling of ConfigMaps was kept for the sake of 
backwards-compatibility. It can be removed as part of the 2.0 efforts.



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

[jira] [Created] (FLINK-33630) CoordinationResponse should be wrapped by SerializedValue in TaskOperatorEventGateway and JobMasterOperatorEventGateway

[Qingsheng Ren (Jira)]

Qingsheng Ren created FLINK-33630:
-

 Summary: CoordinationResponse should be wrapped by SerializedValue 
in TaskOperatorEventGateway and JobMasterOperatorEventGateway
 Key: FLINK-33630
 URL: https://issues.apache.org/jira/browse/FLINK-33630
 Project: Flink
  Issue Type: Bug
  Components: Runtime / Coordination
Affects Versions: 1.17.1, 1.18.0
Reporter: Qingsheng Ren


FLINK-26077 introduced a two-way RPC between operator and coordinator, but 
{{CoordinationResponse}} are not wrapped by {{{}SerializedValue{}}}:

 
[https://github.com/apache/flink/blob/c61c09e464073fae430cab2dd56bd608f9d275fd/flink-rpc/flink-rpc-akka/src/main/java/org/apache/flink/runtime/rpc/pekko/a.java#L254-L255|https://github.com/apache/flink/blob/34620fc5c5698d00e64c6b15f8ce84f807a2e0d7/flink-runtime/src/main/java/org/apache/flink/runtime/jobmaster/JobMasterOperatorEventGateway.java#L54]
 
This might be a problem if the implementation of {{CoordinationResponse}} is 
provided in user code and loaded by user code classloader, because Pekko RPC 
handler always uses app classloader for serializing and deserializing RPC 
parameters and return values, which will lead to {{ClassNotFoundException}} in 
this case. Similar to what we do for the request, we need to wrap a 
{{SerializesValue}} around the response to make sure RPC calls won't cause 
{{{}ClassNotFoundException{}}}.



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

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

[Leonard Xu]

+1 (binding)

- verified signatures
- verified hashsums 
- checked that all POM files point to the same version 1.16.3
- started SQL Client, used MySQL CDC connector to read changelog from database 
, the result is expected
- reviewed the web PR, left minor comment

Best,
Leonard 

> 2023年11月21日 下午8:56，Matthias Pohl  写道：
> 
> +1 (binding)
> 
> * Downloaded artifacts
> * Built Flink from sources
> * Verified SHA512 checksums & GPG signatures
> * Compared checkout with provided sources
> * Verified pom file versions
> * Went over NOTICE/pom file changes without finding anything suspicious
> * Deployed standalone session cluster and ran WordCount example in batch
> and streaming: Nothing suspicious in log files found
> * Verified Java version of uploaded binaries
> 
> Thanks for wrapping 1.16 up. :)
> 
> On Tue, Nov 21, 2023 at 4:55 AM Rui Fan <1996fan...@gmail.com> wrote:
> 
>> +1 (non-binding)
>> 
>> Verified based on this wiki[1].
>> 
>> - Verified signatures and sha512
>> - The source archives do not contain any binaries
>> - Build the source with Maven 3 and java8 (Checked the license as well)
>> - bin/start-cluster.sh with java8, it works fine and no any unexpected LOG
>> - Ran demo, it's fine:  bin/flink run
>> examples/streaming/StateMachineExample.jar
>> 
>> [1]
>> https://cwiki.apache.org/confluence/display/FLINK/Verifying+a+Flink+Release
>> 
>> Best,
>> Rui
>> 
>> On Fri, Nov 17, 2023 at 11:52 AM Yun Tang  wrote:
>> 
>>> +1 (non-binding)
>>> 
>>> 
>>>  *   Verified signatures
>>>  *   Build from source code, and it looks good
>>>  *   Verified that jar packages are built with maven-3.2.5 and JDK8
>>>  *   Reviewed the flink-web PR
>>>  *   Start a local standalone cluster and submit examples
>>> 
>>> Best
>>> Yun Tang
>>> 
>>> From: Rui Fan <1996fan...@gmail.com>
>>> Sent: Monday, November 13, 2023 18:20
>>> To: dev 
>>> Subject: [VOTE] Release 1.16.3, release candidate #1
>>> 
>>> Hi everyone,
>>> 
>>> Please review and vote on the release candidate #1 for the version
>> 1.16.3,
>>> 
>>> 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 B2D64016B940A7E0B9B72E0D7D0528B28037D8BC [3],
>>> 
>>> * all artifacts to be deployed to the Maven Central Repository [4],
>>> 
>>> * source code tag "release-1.16.3-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.
>>> 
>>> 
>>> [1]
>>> 
>>> 
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353259
>>> 
>>> [2] https://dist.apache.org/repos/dist/dev/flink/flink-1.16.3-rc1/
>>> 
>>> [3] https://dist.apache.org/repos/dist/release/flink/KEYS
>>> 
>>> [4]
>>> https://repository.apache.org/content/repositories/orgapacheflink-1670/
>>> 
>>> [5] https://github.com/apache/flink/releases/tag/release-1.16.3-rc1
>>> 
>>> [6] https://github.com/apache/flink-web/pull/698
>>> 
>>> Thanks,
>>> Release Manager
>>> 
>> 

Re: [DISCUSS] Allow TwoPhaseCommittingSink WithPreCommitTopology to alter the type of the Committable

[Péter Váry]

We had a longer discussion with Gordon yesterday.
The main conclusion was that moving to a completely new interface is not
justified, and we try to improve the current one.

Another ask from Gordon was to check when the user will be notified if the
parameter types are incorrect using the mixin approach.
Imagine the type definition below:

private static class TestTwoPhaseCommittingSinkWithPreCommitTopologyWrongMixin
implements
TwoPhaseCommittingSinkWithPreCommitTopology,
WithPreCommitTopology {

The parametrization of the above interfaces contradicts each other:

   - TwoPhaseCommittingSinkWithPreCommitToplogy
  - Input - Interger
  - WriterResult - Long
  - Committable - String)
   - WithPreCommitToplogy
  - WriteResult - Boolean
  - Committable - Void


Sadly, I was not able to find a solution where we could notify the user at
job startup time. The first error the user will get is when the first
record is processed/committed. Talked with Gyula Fora, and we discussed the
possibility to use the TypeExtractor to get the types. We have decided that
it could work in some cases, but would not be a generic solution. See the
"NOTES FOR USERS OF THIS CLASS" [1]

This missing feature would justify abandoning the mixin solution, and
sticking to creating individual interfaces, like:

   - *TwoPhaseCommittingSink* - When no pre-commit topology is needed -
   kept because it is enough for most of the use-cases.
   - *TwoPhaseCommittingSinkWithPreCommitTopology* - When pre-commit
   topology is needed with transformation in the pre commit stage - the new
   generic interface (could be internal)
   - *WithPreWriteTopology* - kept as it is
   - *WithPreCommitTopology* - extends
   TwoPhaseCommittingSinkWithPreCommitTopology with the transformation method
   (classes from streaming package is needed, so can not be merged with
   TwoPhaseCommittingSinkWithPreCommitTopology)
   - *WithPostCommitTopology* - kept as it is (extends only
   TwoPhaseCommittingSink, so no pre-commit topology is allowed)
   - *WithPostCommitTopologyWithPreCommitTopology* - extends
   WithPreCommitTopology with the same method as WithPostCommitTopology

I don't really like the `WithPostCommitTopologyWithPreCommitTopology`
complex interface, and if we start adding new features then the number of
the interfaces could exponentially grow, but I agree that the type checking
is important. I don't have a strong opinion, but I am inclined to vote for
moving in the direction of the individual intefaces.

What do you prefer?

   1. Go with the mixin approach
  1. Better extendability
  2. Fewer interfaces (only with 1 now, but later this could be more)
  3. Easier to understand (IMHO)
   2. Stick with the combined interfaces approach (some mixin, like
   WithPreWriteTopology, some combined like
   WithPostCommitTopologyWithPreCommitTopology)
  1. Better error messages
  2. Less disruptive change (still breaking for implementations of
  WithPreCommitTopology)
   3. Do you have a better idea?


Thanks,
Peter

CC: Jiabao Sun - as he might be interested in this discussion

[1] -
https://nightlies.apache.org/flink/flink-docs-master/api/java/org/apache/flink/api/java/typeutils/TypeExtractor.html


Péter Váry  ezt írta (időpont: 2023. okt. 25.,
Sze, 16:02):

> Hi Gordon,
>
> Thanks for the review, here are my thoughts:
>
> > In terms of the abstraction layering, I was wondering if you've also
> considered this approach which I've quickly sketched in my local fork:
> https://github.com/tzulitai/flink/commit/e84e3ac57ce023c35037a8470fefdfcad877bcae
>
> I think we have a few design issues here:
> - How to handle the old interface where the transformation is not needed
> in the pre-commit phase? - As you have proposed, default method
> implementation is a nice solution here, as we do not really have to change
> everything in the transformation process.
> - How to handle the WithPostCommitTopology interface? - Currently the
> parent interface for the sink with a post commit topology is strictly a
> single interface (TwoPhaseCommittingSink) and we want to add this to both
> type of sinks (new - with transformation / old - without transformation).
> In this case we could get away with creating OldTwoPhaseCommittingSink
> WithPostCommitTopology and NewTwoPhaseCommittingSinkWithPostCommitTopology,
> but this is not a good approach for future extensibility. I tend to prefer
> a real mixin approach to creating multiple interfaces for this.
>
> > Quick thought: regarding the awkwardness you mention in the end with
> sinks that have post commit topologies, but no pre-commit topologies -
> Alternative to the mixin approach in the FLIP, it might make sense to
> consider a builder approach for constructing 2PC sinks
>
> TBH, after providing the possibility to transform in the pre-commit phase,
> I have started to think about the possible different generalizations:
> - Why not have the possibility to have a different 

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

[Sergey Nuyanzin]

+1 (non-binding)

- Downloaded artifacts
- Built Flink from sources
- Verified checksums & signatures
- Verified pom/NOTICE files
- reviewed the web PR

On Thu, Nov 23, 2023 at 12:49 PM Leonard Xu  wrote:

> +1 (binding)
>
> - verified signatures
> - verified hashsums
> - checked all dependency artifacts are 1.17.2
> - started SQL Client, used MySQL CDC connector to read changelog from
> database , the result is expected
> - reviewed the web PR
>
> Best,
> Leonard
>
> > 2023年11月22日 下午11:13，Danny Cranmer  写道：
> >
> > Thanks for driving this release.
> >
> > +1 (binding)
> >
> > - Verified signatures and checksums
> > - Verified there are no binaries in the source archive
> > - Run simple Kinesis job on binary dist, verified consumer, map and
> print.
> > The Flink dashboard looks good.
> > - Built from source successfully
> > - Contents of maven repo looks good
> > - Tag is present in git
> > - Left comments on the web PR
> > - Not a blocker, the copyright header in NOTICE has outdated year, 2022
> > should be 2023 "Copyright 2014-2022 The Apache Software Foundation"
> > - Verified a handful of NOTICE files and they look correct
> >
> > Thanks,
> > Danny
> >
> > On Tue, Nov 21, 2023 at 12:48 PM Matthias Pohl
> >  wrote:
> >
> >> +1 (binding)
> >>
> >> * Downloaded artifacts
> >> * Built Flink from sources
> >> * Verified SHA512 checksums & GPG signatures
> >> * Compared checkout with provided sources
> >> * Verified pom file versions
> >> * Went over NOTICE/pom file changes without finding anything suspicious
> >> * Deployed standalone session cluster and ran WordCount example in batch
> >> and streaming: Nothing suspicious in log files found
> >> * Verified Java version of uploaded binaries
> >>
> >> Thanks Yun Tang for taking care of it.
> >>
> >> On Thu, Nov 16, 2023 at 7:02 AM Rui Fan <1996fan...@gmail.com> wrote:
> >>
> >>> +1 (non-binding)
> >>>
> >>> - Verified signatures
> >>> - Reviewed the flink-web PR, left a couple of comments
> >>> - The source archives do not contain any binaries
> >>> - Build the source with Maven 3 and java8 (Checked the license as well)
> >>> - bin/start-cluster.sh with java8, it works fine and no any unexpected
> >> LOG
> >>> - Ran demo, it's fine:  bin/flink run
> >>> examples/streaming/StateMachineExample.jar
> >>>
> >>> Best,
> >>> Rui
> >>>
> >>> On Mon, Nov 13, 2023 at 4:04 PM Yun Tang  wrote:
> >>>
>  Hi everyone,
> 
>  Please review and vote on the release candidate #1 for the version
> >>> 1.17.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 2E0E1AB5D39D55E608071FB9F795C02A4D2482B3 [3],
> 
>  * all artifacts to be deployed to the Maven Central Repository [4],
> 
>  * source code tag "release-1.17.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.
> 
> 
>  [1]
> 
> >>>
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353260
> 
>  [2] https://dist.apache.org/repos/dist/dev/flink/flink-1.17.2-rc1/
> 
>  [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> 
>  [4]
> 
> >> https://repository.apache.org/content/repositories/orgapacheflink-1669/
> 
>  [5] https://github.com/apache/flink/releases/tag/release-1.17.2-rc1
> 
>  [6] https://github.com/apache/flink-web/pull/696
> 
>  Thanks,
>  Release Manager
> 
> >>>
> >>
>
>

-- 
Best regards,
Sergey

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

[Leonard Xu]

+1 (binding)

- verified signatures
- verified hashsums 
- checked all dependency artifacts are 1.17.2
- started SQL Client, used MySQL CDC connector to read changelog from database 
, the result is expected
- reviewed the web PR

Best,
Leonard

> 2023年11月22日 下午11:13，Danny Cranmer  写道：
> 
> Thanks for driving this release.
> 
> +1 (binding)
> 
> - Verified signatures and checksums
> - Verified there are no binaries in the source archive
> - Run simple Kinesis job on binary dist, verified consumer, map and print.
> The Flink dashboard looks good.
> - Built from source successfully
> - Contents of maven repo looks good
> - Tag is present in git
> - Left comments on the web PR
> - Not a blocker, the copyright header in NOTICE has outdated year, 2022
> should be 2023 "Copyright 2014-2022 The Apache Software Foundation"
> - Verified a handful of NOTICE files and they look correct
> 
> Thanks,
> Danny
> 
> On Tue, Nov 21, 2023 at 12:48 PM Matthias Pohl
>  wrote:
> 
>> +1 (binding)
>> 
>> * Downloaded artifacts
>> * Built Flink from sources
>> * Verified SHA512 checksums & GPG signatures
>> * Compared checkout with provided sources
>> * Verified pom file versions
>> * Went over NOTICE/pom file changes without finding anything suspicious
>> * Deployed standalone session cluster and ran WordCount example in batch
>> and streaming: Nothing suspicious in log files found
>> * Verified Java version of uploaded binaries
>> 
>> Thanks Yun Tang for taking care of it.
>> 
>> On Thu, Nov 16, 2023 at 7:02 AM Rui Fan <1996fan...@gmail.com> wrote:
>> 
>>> +1 (non-binding)
>>> 
>>> - Verified signatures
>>> - Reviewed the flink-web PR, left a couple of comments
>>> - The source archives do not contain any binaries
>>> - Build the source with Maven 3 and java8 (Checked the license as well)
>>> - bin/start-cluster.sh with java8, it works fine and no any unexpected
>> LOG
>>> - Ran demo, it's fine:  bin/flink run
>>> examples/streaming/StateMachineExample.jar
>>> 
>>> Best,
>>> Rui
>>> 
>>> On Mon, Nov 13, 2023 at 4:04 PM Yun Tang  wrote:
>>> 
 Hi everyone,
 
 Please review and vote on the release candidate #1 for the version
>>> 1.17.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 2E0E1AB5D39D55E608071FB9F795C02A4D2482B3 [3],
 
 * all artifacts to be deployed to the Maven Central Repository [4],
 
 * source code tag "release-1.17.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.
 
 
 [1]
 
>>> 
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353260
 
 [2] https://dist.apache.org/repos/dist/dev/flink/flink-1.17.2-rc1/
 
 [3] https://dist.apache.org/repos/dist/release/flink/KEYS
 
 [4]
 
>> https://repository.apache.org/content/repositories/orgapacheflink-1669/
 
 [5] https://github.com/apache/flink/releases/tag/release-1.17.2-rc1
 
 [6] https://github.com/apache/flink-web/pull/696
 
 Thanks,
 Release Manager
 
>>> 
>> 

RE: Apicurio Avro format proposal

[David Radley]

Hi Ryan,
I am reasonable new it this, but here Is my understanding.

If we use pure Avro and Flink SQL, when we create a table – the shape of that 
table is the shape we expect the event to be. This falls down when we evolve 
the schema, i.e. create new versions of the schema. The new versions need to be 
compatible (https://avro.apache.org/docs/1.11.1/specification 
  schema resolution for 
more details).

So if we want a topic to be for a schema then we need to be able to read 
messages that are at different schema versions. The message needs to identify 
which schema version it was written with – so an identifier in a schema 
registry.

In confluent registry there is a magic byte at the start of the message that is 
the schema id, Confluent schema registry can map this to a schema version. 
Using the Confluent Avro format, the serialisers and deserialisers use the 
schema id (the writer schema) to deserialise and the reader schema (e,g, in 
Flink the shape of the table definition) to convert the message appropriately.

In Apicurio, there is a ‘global id’ that identifies the schema version in the 
Apicurio registry.
See 
https://www.apicur.io/registry/docs/apicurio-registry/2.4.x/getting-started/assembly-configuring-kafka-client-serdes.html#registry-serdes-types-avro_registry
 . You will notice that the global id can be in a header or in the message 
payload. It also can be 8 bytes or the legacy 4 bytes. Apicurio also has an 
option to allow it to work with Confluent forms of messages (with the magic 
byte) using option ENABLE_CONFLUENT_ID_HANDLER .

In terms of the issue https://github.com/apache/flink/pull/21805 - it seems to 
be a change to tolerate the presence of bytes from Apicurio (when  
ENABLE_CONFLUENT_ID_HANDLER is specified?). My suggestion is that we close this 
issue and pr; then explicitly create support for Apicurio and document the 
options for a new format with the new Flip that the community agrees with.

In terms of a common base; it looks like we already have 
RegistryAvroDeserializationSchema
and RegistryAvroSerializationSchema as a common base. There might be 
refactoring we can do, when we create the second implementation.

You ask Outside of configuration options, are there different features? They 
are both schema registries that do schema evolution – I think this is a main 
feature they both do, that is relevant to Flink.

Does this help? If I have misrepresented anything – please let me know,

I am investigating further so I can create a well described FLIP for the 
proposed change,
Kind regards, David.


From: Ryan Skraba 
Date: Thursday, 23 November 2023 at 09:55
To: dev@flink.apache.org 
Subject: [EXTERNAL] Re: Apicurio Avro format proposal
Pardon me, I forgot to include that I'd seen this before as
FLINK-26654.  There's a linked JIRA with an open PR that kind of
*plugs in* 8-byte ids . I haven't had the chance to check out Apicurio
yet, but I'm interested in schema registries in general.

All my best, Ryan

[1]: https://github.com/apache/flink/pull/21805
"[FLINK-30721][avro-confluent-registry] Enable 8byte schema id"

On Thu, Nov 23, 2023 at 10:48 AM Ryan Skraba  wrote:
>
> Hello David!
>
> In the FLIP, I'd be interested in knowing how the avro-apicurio and
> avro-confluent formats would differ!  Outside of configuration
> options, are there different features?  Would the two schema registry
> formats have a lot of common base that we could take advantage of?
>
> All my best, Ryan
>
> On Thu, Nov 23, 2023 at 10:14 AM David Radley  wrote:
> >
> > Hi Martijn,
> > Ok will do,
> >   Kind regards, David.
> >
> > From: Martijn Visser 
> > Date: Wednesday, 22 November 2023 at 21:47
> > To: dev@flink.apache.org 
> > Subject: [EXTERNAL] Re: Apicurio Avro format proposal
> > Hi David,
> >
> > Can you create a small FLIP for this?
> >
> > Best regards,
> >
> > Martijn
> >
> > On Wed, Nov 22, 2023 at 6:46 PM David Radley  
> > wrote:
> > >
> > > Hi,
> > > I would like to propose a new Apicurio Avro format.
> > > The Apicurio Avro Schema Registry (avro-apicurio) format would allow you 
> > > to read records that were serialized by the 
> > > io.apicurio.registry.serde.avro.AvroKafkaSerializer and to write records 
> > > that can in turn be read by the 
> > > io.apicurio.registry.serde.avro.AvroKafkaDeserialiser.
> > >
> > > With format options including:
> > >
> > >   *   Apicurio Registry URL
> > >   *   Artifact resolver strategy
> > >   *   ID location
> > >   *   ID encoding
> > >   *   Avro datum provider
> > >   *   Avro encoding
> > >
> > >
> > >
> > > For more details see 
> > > https://www.apicur.io/registry/docs/apicurio-registry/2.4.x/getting-started/assembly-configuring-kafka-client-serdes.html#registry-serdes-types-avro_registry
> > >
> > > I am happy to work on this,
> > >   Kind regards, David.
> > >
> > > Unless otherwise stated above:
> > >
> > > IBM United Kingdom Limited
> > > Registered in 

[jira] [Created] (FLINK-33629) Introduce ArchTest rules to ban Junit 4 for modules already completed the migration

[Jiabao Sun (Jira)]

Jiabao Sun created FLINK-33629:
--

 Summary: Introduce ArchTest rules to ban Junit 4 for modules 
already completed the migration
 Key: FLINK-33629
 URL: https://issues.apache.org/jira/browse/FLINK-33629
 Project: Flink
  Issue Type: Sub-task
  Components: Tests
Affects Versions: 1.18.0
Reporter: Jiabao Sun


Currently, many modules have already completed the migration to JUnit 5, and we 
need to prevent the introduction of JUnit 4 tests in new PRs. 

However, completely removing the dependency on JUnit 4 is challenging. It 
requires defining JUnit 4 as optional in the flink-parent module and allowing 
sub-modules to selectively include it. However, this approach still cannot 
solve the issue of transitive dependencies. 

Therefore, considering introducing new rules in ArchTest to prohibit the usage 
of JUnit 4 in modules that have already completed the migration.





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

[jira] [Created] (FLINK-33628) Upgrading Flink's default ZooKeeper version to 3.8.3

[Matthias Pohl (Jira)]

Matthias Pohl created FLINK-33628:
-

 Summary: Upgrading Flink's default ZooKeeper version to 3.8.3
 Key: FLINK-33628
 URL: https://issues.apache.org/jira/browse/FLINK-33628
 Project: Flink
  Issue Type: Improvement
  Components: Runtime / Coordination
Affects Versions: 1.19.0
Reporter: Matthias Pohl


Flink currently supports ZooKeeper 3.7.1 as its default version which was added 
in Flink 1.17 (FLINK-29420). The ZooKeeper project released 3.8 and 3.9 in the 
meantime. 3.7 will reach its EOL with a new minor release. ZooKeeper 3.8 is 
already provided by \{{flink-shaded}} and, therefore, allows most likely an 
easy switch.

This issue is about chaning to ZooKeeper 3.8.3. A final discussion should be 
initiated in the mailing list before merging the change.



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

Re: [DISCUSS] Towards flink-shaded release 18.0

[Matthias Pohl]

+1

Thanks for driving this, Sergey. We could also think of removing the
ZooKeeper versions 3.5 and 3.6, I guess. 3.6 reached EOL in 2022. Flink
1.17 already switched to 3.7 as the default version.

On Thu, Nov 23, 2023 at 9:31 AM Jing Ge  wrote:

> +1
>
> Does it make sense to use 32.1.3-jre Guava?
>
> Best regards,
> Jing
>
> On Thu, Nov 23, 2023 at 8:42 AM Yun Tang  wrote:
>
> > +1, thanks Sergey for driving this work.
> >
> > Best
> > Yun Tang
> > 
> > From: Leonard Xu 
> > Sent: Thursday, November 23, 2023 9:38
> > To: dev 
> > Subject: Re: [DISCUSS] Towards flink-shaded release 18.0
> >
> > +1, thanks Sergey for driving this.
> >
> > > 2023年11月23日 上午5:46，Martijn Visser  写道：
> > >
> > > +1. More than happy to help :)
> > >
> > > On Wed, Nov 22, 2023 at 9:16 PM Sergey Nuyanzin 
> > wrote:
> > >>
> > >> Hi everyone,
> > >>
> > >> I would like to start discussion about creating a new 18 release for
> > >> flink-shaded[1].
> > >>
> > >> Among others it brings fix for ZooKeeper CVE [2],
> > >> a couple of Guava CVEs [3], [4]
> > >> and support of jdk 21 from netty mentioned in one of
> > >> the java 21[5] support subtasks [6]
> > >>
> > >> Also making a release now will allow to have enough time
> > >> for testing before Flink 1.19 release.
> > >>
> > >> I would volunteer to make the release happen
> > >> however probably I guess I will need some PMC help
> > >>
> > >>
> > >> [1] https://github.com/apache/flink-shaded
> > >> [2] https://nvd.nist.gov/vuln/detail/CVE-2023-44981
> > >> [3] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-2976
> > >> [4] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8908
> > >> [5] https://issues.apache.org/jira/browse/FLINK-33163
> > >> [6] https://issues.apache.org/jira/browse/FLINK-1
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >> --
> > >> Best regards,
> > >> Sergey
> >
> >
>

Re: Apicurio Avro format proposal

[Ryan Skraba]

Pardon me, I forgot to include that I'd seen this before as
FLINK-26654.  There's a linked JIRA with an open PR that kind of
*plugs in* 8-byte ids . I haven't had the chance to check out Apicurio
yet, but I'm interested in schema registries in general.

All my best, Ryan

[1]: https://github.com/apache/flink/pull/21805
"[FLINK-30721][avro-confluent-registry] Enable 8byte schema id"

On Thu, Nov 23, 2023 at 10:48 AM Ryan Skraba  wrote:
>
> Hello David!
>
> In the FLIP, I'd be interested in knowing how the avro-apicurio and
> avro-confluent formats would differ!  Outside of configuration
> options, are there different features?  Would the two schema registry
> formats have a lot of common base that we could take advantage of?
>
> All my best, Ryan
>
> On Thu, Nov 23, 2023 at 10:14 AM David Radley  wrote:
> >
> > Hi Martijn,
> > Ok will do,
> >   Kind regards, David.
> >
> > From: Martijn Visser 
> > Date: Wednesday, 22 November 2023 at 21:47
> > To: dev@flink.apache.org 
> > Subject: [EXTERNAL] Re: Apicurio Avro format proposal
> > Hi David,
> >
> > Can you create a small FLIP for this?
> >
> > Best regards,
> >
> > Martijn
> >
> > On Wed, Nov 22, 2023 at 6:46 PM David Radley  
> > wrote:
> > >
> > > Hi,
> > > I would like to propose a new Apicurio Avro format.
> > > The Apicurio Avro Schema Registry (avro-apicurio) format would allow you 
> > > to read records that were serialized by the 
> > > io.apicurio.registry.serde.avro.AvroKafkaSerializer and to write records 
> > > that can in turn be read by the 
> > > io.apicurio.registry.serde.avro.AvroKafkaDeserialiser.
> > >
> > > With format options including:
> > >
> > >   *   Apicurio Registry URL
> > >   *   Artifact resolver strategy
> > >   *   ID location
> > >   *   ID encoding
> > >   *   Avro datum provider
> > >   *   Avro encoding
> > >
> > >
> > >
> > > For more details see 
> > > https://www.apicur.io/registry/docs/apicurio-registry/2.4.x/getting-started/assembly-configuring-kafka-client-serdes.html#registry-serdes-types-avro_registry
> > >
> > > I am happy to work on this,
> > >   Kind regards, David.
> > >
> > > Unless otherwise stated above:
> > >
> > > IBM United Kingdom Limited
> > > Registered in England and Wales with number 741598
> > > Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU
> >
> > Unless otherwise stated above:
> >
> > IBM United Kingdom Limited
> > Registered in England and Wales with number 741598
> > Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU

Re: Apicurio Avro format proposal

[Ryan Skraba]

Hello David!

In the FLIP, I'd be interested in knowing how the avro-apicurio and
avro-confluent formats would differ!  Outside of configuration
options, are there different features?  Would the two schema registry
formats have a lot of common base that we could take advantage of?

All my best, Ryan

On Thu, Nov 23, 2023 at 10:14 AM David Radley  wrote:
>
> Hi Martijn,
> Ok will do,
>   Kind regards, David.
>
> From: Martijn Visser 
> Date: Wednesday, 22 November 2023 at 21:47
> To: dev@flink.apache.org 
> Subject: [EXTERNAL] Re: Apicurio Avro format proposal
> Hi David,
>
> Can you create a small FLIP for this?
>
> Best regards,
>
> Martijn
>
> On Wed, Nov 22, 2023 at 6:46 PM David Radley  wrote:
> >
> > Hi,
> > I would like to propose a new Apicurio Avro format.
> > The Apicurio Avro Schema Registry (avro-apicurio) format would allow you to 
> > read records that were serialized by the 
> > io.apicurio.registry.serde.avro.AvroKafkaSerializer and to write records 
> > that can in turn be read by the 
> > io.apicurio.registry.serde.avro.AvroKafkaDeserialiser.
> >
> > With format options including:
> >
> >   *   Apicurio Registry URL
> >   *   Artifact resolver strategy
> >   *   ID location
> >   *   ID encoding
> >   *   Avro datum provider
> >   *   Avro encoding
> >
> >
> >
> > For more details see 
> > https://www.apicur.io/registry/docs/apicurio-registry/2.4.x/getting-started/assembly-configuring-kafka-client-serdes.html#registry-serdes-types-avro_registry
> >
> > I am happy to work on this,
> >   Kind regards, David.
> >
> > Unless otherwise stated above:
> >
> > IBM United Kingdom Limited
> > Registered in England and Wales with number 741598
> > Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU
>
> Unless otherwise stated above:
>
> IBM United Kingdom Limited
> Registered in England and Wales with number 741598
> Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU

Re: [DISCUSS] FLIP-395: Migration to GitHub Actions

[Matthias Pohl]

Btw. even though we've been focusing on GitHub Actions with this FLIP, I'm
curious whether somebody has experience with Apache Infra's Jenkins
deployment. The discussion I found about Jenkins [1] is quite out-dated
(2014). I haven't worked with it myself but could imagine that there are
some features provided through plugins which are missing in GitHub Actions.

[1] https://lists.apache.org/thread/vs81xdhn3q777r7x9k7wd4dyl9kvoqn4

On Tue, Nov 21, 2023 at 4:19 PM Matthias Pohl 
wrote:

> That's a valid point. I updated the FLIP accordingly:
>
>> Currently, the secrets (e.g. for S3 access tokens) are maintained by
>> certain PMC members with access to the corresponding configuration in the
>> Azure CI project. This responsibility will be moved to Apache Infra. They
>> are in charge of handling secrets in the Apache organization. As a
>> consequence, updating secrets is becoming a bit more complicated. This can
>> be still considered an improvement from a legal standpoint because the
>> responsibility is transferred from an individual company (i.e. Ververica
>> who's the maintainer of the Azure CI project) to the Apache Foundation.
>
>
> On Tue, Nov 21, 2023 at 3:37 PM Martijn Visser 
> wrote:
>
>> Hi Matthias,
>>
>> Thanks for the write-up and for the efforts on this. I really hope
>> that we can move away from Azure towards GHA for a better integration
>> as well (directly seeing if a PR can be merged due to CI passing for
>> example).
>>
>> The one thing I'm missing in the FLIP is how we would setup the
>> secrets for the nightly runs (for the S3 tests, potential tests with
>> external services etc). My guess is we need to provide the secret to
>> ASF Infra and then we would be able to refer to them in a pipeline?
>>
>> Best regards,
>>
>> Martijn
>>
>> On Tue, Nov 21, 2023 at 3:05 PM Matthias Pohl
>>  wrote:
>> >
>> > I realized that I mixed up FLIP IDs. FLIP-395 is already reserved [1]. I
>> > switched to FLIP-396 [2] for the sake of consistency. 8)
>> >
>> > [1] https://lists.apache.org/thread/wjd3nbvg6nt93lb0sd52f0lzls6559tv
>> > [2]
>> >
>> https://cwiki.apache.org/confluence/display/FLINK/FLIP-396%3A+Migration+to+GitHub+Actions
>> >
>> > On Tue, Nov 21, 2023 at 2:58 PM Matthias Pohl 
>> > wrote:
>> >
>> > > Hi everyone,
>> > >
>> > > The Flink community discussed migrating from Azure CI to GitHub
>> Actions
>> > > quite some time ago [1]. The efforts around that stalled due to
>> limitations
>> > > around self-hosted runner support from Apache Infra’s side. There
>> were some
>> > > recent developments on that topic. Apache Infra is experimenting with
>> > > ephemeral runners now which might enable us to move ahead with GitHub
>> > > Actions.
>> > >
>> > > The goal is to join the trial phase for ephemeral runners and
>> experiment
>> > > with our CI workflows in terms of stability and performance. At the
>> end we
>> > > can decide whether we want to abandon Azure CI and move to GitHub
>> Actions
>> > > or stick to the former one.
>> > >
>> > > Nico Weidner and Chesnay laid the groundwork on this topic in the
>> past. I
>> > > picked up the work they did and continued experimenting with it in my
>> own
>> > > fork XComp/flink [2] the past few weeks. The workflows are in a state
>> where
>> > > I think that we start moving the relevant code into Flink’s
>> repository.
>> > > Example runs for the basic workflow [3] and the extended (nightly)
>> workflow
>> > > [4] are provided.
>> > >
>> > > This will bring a few more changes to the Flink contributors. That is
>> why
>> > > I wanted to bring this discussion to the mailing list first. I did a
>> write
>> > > up on (hopefully) all related topics in FLIP-395 [5].
>> > >
>> > > I’m looking forward to your feedback.
>> > >
>> > > Matthias
>> > >
>> > > [1] https://lists.apache.org/thread/vcyx2nx0mhklqwm827vgykv8pc54gg3k
>> > >
>> > > [2] https://github.com/XComp/flink/actions
>> > >
>> > > [3] https://github.com/XComp/flink/actions/runs/6926309782
>> > >
>> > > [4] https://github.com/XComp/flink/actions/runs/6927443941
>> > >
>> > > [5]
>> > >
>> https://cwiki.apache.org/confluence/display/FLINK/FLIP-395%3A+Migration+to+GitHub+Actions
>> > >
>> > >
>> > > --
>> > >
>> > > [image: Aiven] 
>> > >
>> > > *Matthias Pohl*
>> > > Opensource Software Engineer, *Aiven*
>> > > matthias.p...@aiven.io|  +49 170 9869525
>> > > aiven.io    |
>> > > 
>> > >    <
>> https://twitter.com/aiven_io>
>> > > *Aiven Deutschland GmbH*
>> > > Alexanderufer 3-7, 10117 Berlin
>> > > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen
>> > > Amtsgericht Charlottenburg, HRB 209739 B
>> > >
>>
>

RE: Apicurio Avro format proposal

[David Radley]

Hi Martijn,
Ok will do,
  Kind regards, David.

From: Martijn Visser 
Date: Wednesday, 22 November 2023 at 21:47
To: dev@flink.apache.org 
Subject: [EXTERNAL] Re: Apicurio Avro format proposal
Hi David,

Can you create a small FLIP for this?

Best regards,

Martijn

On Wed, Nov 22, 2023 at 6:46 PM David Radley  wrote:
>
> Hi,
> I would like to propose a new Apicurio Avro format.
> The Apicurio Avro Schema Registry (avro-apicurio) format would allow you to 
> read records that were serialized by the 
> io.apicurio.registry.serde.avro.AvroKafkaSerializer and to write records that 
> can in turn be read by the 
> io.apicurio.registry.serde.avro.AvroKafkaDeserialiser.
>
> With format options including:
>
>   *   Apicurio Registry URL
>   *   Artifact resolver strategy
>   *   ID location
>   *   ID encoding
>   *   Avro datum provider
>   *   Avro encoding
>
>
>
> For more details see 
> https://www.apicur.io/registry/docs/apicurio-registry/2.4.x/getting-started/assembly-configuring-kafka-client-serdes.html#registry-serdes-types-avro_registry
>
> I am happy to work on this,
>   Kind regards, David.
>
> Unless otherwise stated above:
>
> IBM United Kingdom Limited
> Registered in England and Wales with number 741598
> Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU

Unless otherwise stated above:

IBM United Kingdom Limited
Registered in England and Wales with number 741598
Registered office: PO Box 41, North Harbour, Portsmouth, Hants. PO6 3AU

Re: [DISCUSS] REST API behaviour when user main method throws error

[Danny Cranmer]

Hey David,

Thanks for the feedback.

> For streaming, this is probably something we could address by
book-keeping jobs submitted by the jar and canceling them on exception.

I considered two options. 1/ cancel on error as you proposed. This has the
downside that it could start processing data temporarily. 2/ Stage the job,
but do not submit until the main() method completes. This way we could
ensure the main method completes before actually starting the job, however
would increase startup latency.

> A bigger problem is that the main method could have the side-effects that
you don't know how to roll-back.

This is true, and might be somewhat complex to solve fully. Getting the
Flink bits right we do control is more important in my opinion.

Right now we will continue to work around this in the client and consider
drafting a FLIP.

Thanks,
Danny

On Mon, Nov 20, 2023 at 4:56 PM David Morávek  wrote:

> Hi Danny,
>
> > My current proposal is that the REST API should not leave the Flink
> cluster
> in an inconsistent state.
>
> Regarding consistency, Flink only cares about individual jobs, but I can
> see your point.
>
> For streaming, this is probably something we could address by book-keeping
> jobs submitted by the jar and canceling them on exception. This is not
> prone to JM failure and would be subject to bug reports because there are
> no guarantees (it could be addressed; it's not straightforward; we've spent
> years getting this correct for Application mode).
>
> A bigger problem is that the main method could have the side-effects that
> you don't know how to roll-back. For example, creating directories for
> batch outputs and moving files. To make this 100% correct, we'd need to
> introduce a new set of client-facing APIs.
>
> I'm unaware of any framework that did this right (MR, Spark, etc had
> the same issue); you must solve HA for drivers/client programs first.
>
> These are quick thoughts; something simple that works for 90% might be
> worth pursuing, ignoring the corner cases.
>
> Best,
> D.
>
> On Tue, Nov 14, 2023 at 10:00 AM Danny Cranmer 
> wrote:
>
> > Hey all,
> >
> > We run Flink clusters in session mode; we upload the user jar and then
> > invoke "/jars/:jarid/run" [1] REST API endpoint. We have noticed a
> > discrepancy in the run endpoint and were hoping to get some feedback from
> > the community before proposing a FLIP or Jira to fix it.
> >
> > Some problem context: The "/jars/:jarid/run" endpoint runs the main()
> > method in the user jar. When the call is successful the API will return
> the
> > job ID (case 1). When the call throws an error, the API will return the
> > error message (case 2). If a job is submitted successfully AND it throws
> an
> > error, the result is a running job but the API returns the error message
> > (case 3). There are two common cases that can result in this failure
> mode:
> > 1/ the user code attempts to run multiple jobs, the first is successful
> and
> > the second is rejected [2]. 2/ the user code throws an arbitrary
> exception
> > after successfully submitting a job. Reproduction code for both is
> included
> > below. For case 3 the client must 1/ run a jar, 2/ query for running jobs
> > and 3/ decide how to proceed, either cleaning up or marking it as
> > successful. This is overloading the responsibility of the client.
> >
> > My current proposal is that the REST API should not leave the Flink
> cluster
> > in an inconsistent state. If the run command is successful we should
> have a
> > running job, if the run command fails, we should not have any running
> jobs.
> > There are a few ways to achieve this, but I would like to leave that
> > discussion to the FLIP. Right now I am looking for feedback on the
> desired
> > API behaviour.
> >
> > 1/ The user code attempts to run multiple jobs (Flink 1.15)
> >
> > public class MultipleJobs {
> > public static final long ROWS_PER_SECOND = 1;
> > public static final long TOTAL_ROWS = 1_000_000;
> >
> > public static void main(String[] args) throws Exception {
> >
> > StreamExecutionEnvironment env = StreamExecutionEnvironment.
> > getExecutionEnvironment();
> >
> > env.addSource(new DataGeneratorSource<>(stringGenerator(32),
> > ROWS_PER_SECOND,
> > TOTAL_ROWS))
> > .returns(String.class)
> > .print();
> >
> > env.execute("Job #1");
> >
> > env.addSource(new DataGeneratorSource<>(stringGenerator(32),
> > ROWS_PER_SECOND,
> > TOTAL_ROWS))
> > .returns(String.class)
> > .print();
> >
> > env.execute("Job #2");
> > }
> > }
> >
> >
> > 2/ The user code throws an arbitrary exception after successfully
> > submitting a job (Flink 1.15)
> >
> > public class CustomerErrorJobSubmission {
> > public static final long ROWS_PER_SECOND = 1;
> > public static final long TOTAL_ROWS = 1_000_000;
> >
> > public static void main(String[] args) throws Exception {
> >
> > StreamExecutionEnvironment env =
> > StreamExecutionEnvironment.getExecutionEnvironment();
> >
> > 

[jira] [Created] (FLINK-33627) Bump snappy-java to 1.1.10.4 in flink-statefun

[Ryan Skraba (Jira)]

Ryan Skraba created FLINK-33627:
---

 Summary: Bump snappy-java to 1.1.10.4 in flink-statefun
 Key: FLINK-33627
 URL: https://issues.apache.org/jira/browse/FLINK-33627
 Project: Flink
  Issue Type: Bug
  Components: Stateful Functions
Affects Versions: statefun-3.3.0
Reporter: Ryan Skraba


Xerial published a security alert for a Denial of Service attack that [exists 
on 
1.1.10.1|https://github.com/xerial/snappy-java/security/advisories/GHSA-55g7-9cwv-5qfv].

See FLINK-33149 for flink core and connectors.



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

Re: [VOTE] FLIP-386: Support adding custom metrics in Recovery Spans

[Roman Khachatryan]

+1 (binding)

Regards,
Roman


On Wed, Nov 22, 2023 at 12:55 PM Rui Fan <1996fan...@gmail.com> wrote:

> +1(binding)
>
> Thanks for driving this  proposal!
>
> Best,
> Rui
>
> On Wed, Nov 22, 2023 at 7:44 PM Piotr Nowojski 
> wrote:
>
> > Hi All,
> >
> > I'd like to start a vote on the FLIP-386: Support adding custom metrics
> in
> > Recovery Spans [1]. The discussion thread is here [2].
> >
> > The vote will be open for at least 72 hours unless there is an objection
> or
> > not enough votes.
> >
> > [1] https://cwiki.apache.org/confluence/x/VAuZE
> > [2] https://lists.apache.org/thread/zt4ykyhv6cco83j9hjngn52b1oprj1tv
> >
>

Re: [DISCUSS] Towards flink-shaded release 18.0

[Jing Ge]

+1

Does it make sense to use 32.1.3-jre Guava?

Best regards,
Jing

On Thu, Nov 23, 2023 at 8:42 AM Yun Tang  wrote:

> +1, thanks Sergey for driving this work.
>
> Best
> Yun Tang
> 
> From: Leonard Xu 
> Sent: Thursday, November 23, 2023 9:38
> To: dev 
> Subject: Re: [DISCUSS] Towards flink-shaded release 18.0
>
> +1, thanks Sergey for driving this.
>
> > 2023年11月23日 上午5:46，Martijn Visser  写道：
> >
> > +1. More than happy to help :)
> >
> > On Wed, Nov 22, 2023 at 9:16 PM Sergey Nuyanzin 
> wrote:
> >>
> >> Hi everyone,
> >>
> >> I would like to start discussion about creating a new 18 release for
> >> flink-shaded[1].
> >>
> >> Among others it brings fix for ZooKeeper CVE [2],
> >> a couple of Guava CVEs [3], [4]
> >> and support of jdk 21 from netty mentioned in one of
> >> the java 21[5] support subtasks [6]
> >>
> >> Also making a release now will allow to have enough time
> >> for testing before Flink 1.19 release.
> >>
> >> I would volunteer to make the release happen
> >> however probably I guess I will need some PMC help
> >>
> >>
> >> [1] https://github.com/apache/flink-shaded
> >> [2] https://nvd.nist.gov/vuln/detail/CVE-2023-44981
> >> [3] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-2976
> >> [4] https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8908
> >> [5] https://issues.apache.org/jira/browse/FLINK-33163
> >> [6] https://issues.apache.org/jira/browse/FLINK-1
> >>
> >>
> >>
> >>
> >>
> >>
> >> --
> >> Best regards,
> >> Sergey
>
>

[jira] [Created] (FLINK-33626) Wrong style in flink ui

[Fang Yong (Jira)]

Fang Yong created FLINK-33626:
-

 Summary: Wrong style in flink ui
 Key: FLINK-33626
 URL: https://issues.apache.org/jira/browse/FLINK-33626
 Project: Flink
  Issue Type: Bug
  Components: Travis
Affects Versions: 1.19.0
Reporter: Fang Yong
 Attachments: image-2023-11-23-16-06-44-000.png

https://nightlies.apache.org/flink/flink-docs-master/

 !image-2023-11-23-16-06-44-000.png! 



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

[jira] [Created] (FLINK-33625) FLIP-390: Support System out and err to be redirected to LOG or discarded

[Rui Fan (Jira)]

Rui Fan created FLINK-33625:
---

 Summary: FLIP-390: Support System out and err to be redirected to 
LOG or discarded
 Key: FLINK-33625
 URL: https://issues.apache.org/jira/browse/FLINK-33625
 Project: Flink
  Issue Type: New Feature
  Components: Runtime / Configuration
Reporter: Rui Fan
Assignee: Rui Fan
 Fix For: 1.19.0


Get more from https://cwiki.apache.org/confluence/x/4guZE



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