Re: [ANNOUNCE] Apache Paimon is graduated to Top Level Project

[Yu Li]

CC the Flink user and dev mailing list.

Paimon originated within the Flink community, initially known as Flink
Table Store, and all our incubating mentors are members of the Flink
Project Management Committee. I am confident that the bonds of
enduring friendship and close collaboration will continue to unite the
two communities.

And congratulations all!

Best Regards,
Yu

On Wed, 27 Mar 2024 at 20:35, Guojun Li  wrote:
>
> Congratulations!
>
> Best,
> Guojun
>
> On Wed, Mar 27, 2024 at 5:24 PM wulin  wrote:
>
> > Congratulations~
> >
> > > 2024年3月27日 15:54，王刚  写道：
> > >
> > > Congratulations~
> > >
> > >> 2024年3月26日 10:25，Jingsong Li  写道：
> > >>
> > >> Hi Paimon community,
> > >>
> > >> I’m glad to announce that the ASF board has approved a resolution to
> > >> graduate Paimon into a full Top Level Project. Thanks to everyone for
> > >> your help to get to this point.
> > >>
> > >> I just created an issue to track the things we need to modify [2],
> > >> please comment on it if you feel that something is missing. You can
> > >> refer to apache documentation [1] too.
> > >>
> > >> And, we already completed the GitHub repo migration [3], please update
> > >> your local git repo to track the new repo [4].
> > >>
> > >> You can run the following command to complete the remote repo tracking
> > >> migration.
> > >>
> > >> git remote set-url origin https://github.com/apache/paimon.git
> > >>
> > >> If you have a different name, please change the 'origin' to your remote
> > name.
> > >>
> > >> Please join me in celebrating!
> > >>
> > >> [1]
> > https://incubator.apache.org/guides/transferring.html#life_after_graduation
> > >> [2] https://github.com/apache/paimon/issues/3091
> > >> [3] https://issues.apache.org/jira/browse/INFRA-25630
> > >> [4] https://github.com/apache/paimon
> > >>
> > >> Best,
> > >> Jingsong Lee
> >
> >

Re: [ANNOUNCE] Donation Flink CDC into Apache Flink has Completed

[Yu Li]

Congratulations and look forward to its further development!

Best Regards,
Yu

On Thu, 21 Mar 2024 at 15:54, ConradJam  wrote:
>
> Congrattulations!
>
> Leonard Xu  于2024年3月20日周三 21:36写道：
>
> > Hi devs and users,
> >
> > We are thrilled to announce that the donation of Flink CDC as a
> > sub-project of Apache Flink has completed. We invite you to explore the new
> > resources available:
> >
> > - GitHub Repository: https://github.com/apache/flink-cdc
> > - Flink CDC Documentation:
> > https://nightlies.apache.org/flink/flink-cdc-docs-stable
> >
> > After Flink community accepted this donation[1], we have completed
> > software copyright signing, code repo migration, code cleanup, website
> > migration, CI migration and github issues migration etc.
> > Here I am particularly grateful to Hang Ruan, Zhongqaing Gong, Qingsheng
> > Ren, Jiabao Sun, LvYanquan, loserwang1024 and other contributors for their
> > contributions and help during this process！
> >
> >
> > For all previous contributors: The contribution process has slightly
> > changed to align with the main Flink project. To report bugs or suggest new
> > features, please open tickets
> > Apache Jira (https://issues.apache.org/jira).  Note that we will no
> > longer accept GitHub issues for these purposes.
> >
> >
> > Welcome to explore the new repository and documentation. Your feedback and
> > contributions are invaluable as we continue to improve Flink CDC.
> >
> > Thanks everyone for your support and happy exploring Flink CDC!
> >
> > Best，
> > Leonard
> > [1] https://lists.apache.org/thread/cw29fhsp99243yfo95xrkw82s5s418ob
> >
> >
>
> --
> Best
>
> ConradJam

Re: [ANNOUNCE] Apache Flink 1.19.0 released

[Yu Li]

Congrats and thanks all for the efforts!

Best Regards,
Yu

On Tue, 19 Mar 2024 at 11:51, gongzhongqiang  wrote:
>
> Congrats! Thanks to everyone involved!
>
> Best,
> Zhongqiang Gong
>
> Lincoln Lee  于2024年3月18日周一 16:27写道：
>>
>> The Apache Flink community is very happy to announce the release of Apache
>> Flink 1.19.0, which is the fisrt release for the Apache Flink 1.19 series.
>>
>> Apache Flink® is an open-source stream processing framework for
>> distributed, high-performing, always-available, and accurate data streaming
>> applications.
>>
>> The release is available for download at:
>> https://flink.apache.org/downloads.html
>>
>> Please check out the release blog post for an overview of the improvements
>> for this bugfix release:
>> https://flink.apache.org/2024/03/18/announcing-the-release-of-apache-flink-1.19/
>>
>> The full release notes are available in Jira:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12353282
>>
>> We would like to thank all contributors of the Apache Flink community who
>> made this release possible!
>>
>>
>> Best,
>> Yun, Jing, Martijn and Lincoln

Re: [VOTE] Accept Flink CDC into Apache Flink

[Yu Li]

+1 (binding)

Good luck!

Best Regards,
Yu


On Tue, 9 Jan 2024 at 16:49, Rui Fan <1996fan...@gmail.com> wrote:

> +1 (non-binding)
>
> Best,
> Rui
>
> On Tue, Jan 9, 2024 at 4:41 PM Hang Ruan  wrote:
>
> > +1 (non-binding)
> >
> > Best,
> > Hang
> >
> > gongzhongqiang  于2024年1月9日周二 16:25写道：
> >
> > > +1 non-binding
> > >
> > > Best,
> > > Zhongqiang
> > >
> > > Leonard Xu  于2024年1月9日周二 15:05写道：
> > >
> > > > Hello all,
> > > >
> > > > This is the official vote whether to accept the Flink CDC code
> > > contribution
> > > >  to Apache Flink.
> > > >
> > > > The current Flink CDC code, documentation, and website can be
> > > > found here:
> > > > code: https://github.com/ververica/flink-cdc-connectors <
> > > > https://github.com/ververica/flink-cdc-connectors>
> > > > docs: https://ververica.github.io/flink-cdc-connectors/ <
> > > > https://ververica.github.io/flink-cdc-connectors/>
> > > >
> > > > This vote should capture whether the Apache Flink community is
> > interested
> > > > in accepting, maintaining, and evolving Flink CDC.
> > > >
> > > > Regarding my original proposal[1] in the dev mailing list, I firmly
> > > believe
> > > > that this initiative aligns perfectly with Flink. For the Flink
> > > community,
> > > > it represents an opportunity to bolster Flink's competitive edge in
> > > > streaming
> > > > data integration, fostering the robust growth and prosperity of the
> > > Apache
> > > > Flink
> > > > ecosystem. For the Flink CDC project, becoming a sub-project of
> Apache
> > > > Flink
> > > > means becoming an integral part of a neutral open-source community,
> > > > capable of
> > > > attracting a more diverse pool of contributors.
> > > >
> > > > All Flink CDC maintainers are dedicated to continuously contributing
> to
> > > > achieve
> > > > seamless integration with Flink. Additionally, PMC members like Jark,
> > > > Qingsheng,
> > > > and I are willing to infacilitate the expansion of contributors and
> > > > committers to
> > > > effectively maintain this new sub-project.
> > > >
> > > > This is a "Adoption of a new Codebase" vote as per the Flink bylaws
> > [2].
> > > > Only PMC votes are binding. The vote will be open at least 7 days
> > > > (excluding weekends), meaning until Thursday January 18 12:00 UTC, or
> > > > until we
> > > > achieve the 2/3rd majority. We will follow the instructions in the
> > Flink
> > > > Bylaws
> > > > in the case of insufficient active binding voters:
> > > >
> > > > > 1. Wait until the minimum length of the voting passes.
> > > > > 2. Publicly reach out via personal email to the remaining binding
> > > voters
> > > > in the
> > > > voting mail thread for at least 2 attempts with at least 7 days
> between
> > > > two attempts.
> > > > > 3. If the binding voter being contacted still failed to respond
> after
> > > > all the attempts,
> > > > the binding voter will be considered as inactive for the purpose of
> > this
> > > > particular voting.
> > > >
> > > > Welcome voting !
> > > >
> > > > Best,
> > > > Leonard
> > > > [1] https://lists.apache.org/thread/o7klnbsotmmql999bnwmdgo56b6kxx9l
> > > > [2]
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=120731026
> > >
> >
>

Re: [PROPOSAL] Contribute Flink CDC Connectors project to Apache Flink

[Yu Li]

+1

Thanks Leonard for the proposal, and all Flink CDC contributors for the
existing great works. I believe these two projects are a perfect fit and
the donation will benifit both.

Best Regards,
Yu


On Fri, Dec 8, 2023 at 2:49 PM bai_wentao1  wrote:

> +1 for this exciting work
>
>
> Best regards,
> WT
>
>
> | |
> bai_wentao1
> |
> |
> bai_went...@163.com
> |
>  Replied Message 
> | From | ConradJam |
> | Date | 12/8/2023 14:26 |
> | To |  |
> | Subject | Re: [PROPOSAL] Contribute Flink CDC Connectors project to
> Apache Flink |
> +1 Best Idea . Thanks to all the contributors of Flink CDC for the great
> work.
>
> yuxia  于2023年12月7日周四 20:46写道：
>
> +1 for this. Thanks all the contributors of Flink CDC for the great work.
>
> Best regards,
> Yuxia
>
> - 原始邮件 -
> 发件人: "Martijn Visser" 
> 收件人: "dev" 
> 发送时间: 星期四, 2023年 12 月 07日 下午 8:14:36
> 主题: Re: [PROPOSAL] Contribute Flink CDC Connectors project to Apache Flink
>
> Hi Leonard,
>
> +1 for this. I think the CDC connectors are a great result and example
> of the Flink CDC community. Kudos to you all.
>
> Best regards,
>
> Martijn
>
> On Thu, Dec 7, 2023 at 10:40 AM Márton Balassi 
> wrote:
>
> Hi Leonard,
>
> Thank you for the excellent work you and the team working on the CDC
> connectors project have been doing so far. I am +1 of having them under
> Flink's umbrella.
>
> On Thu, Dec 7, 2023 at 10:26 AM Etienne Chauchot 
> wrote:
>
> Big +1, thanks this will be a very useful addition to Flink.
>
> Best
>
> Etienne
>
> Le 07/12/2023 à 09:26, Hang Ruan a écrit :
> +1 for contributing CDC Connectors  to Apache Flink.
>
> Best,
> Hang
>
> Yuxin Tan  于2023年12月7日周四 16:05写道：
>
> Cool, +1 for contributing CDC Connectors to Apache Flink.
>
> Best,
> Yuxin
>
>
> Jing Ge  于2023年12月7日周四 15:43写道：
>
> Awesome! +1
>
> Best regards,
> Jing
>
> On Thu, Dec 7, 2023 at 8:34 AM Sergey Nuyanzin
> wrote:
>
> thanks for working on this and driving it
>
> +1
>
> On Thu, Dec 7, 2023 at 7:26 AM Feng Jin
> wrote:
>
> This is incredibly exciting news, a big +1 for this.
>
> Thank you for the fantastic work on Flink CDC. We have created
> thousands
> of
> real-time integration jobs using Flink CDC connectors.
>
>
> Best,
> Feng
>
> On Thu, Dec 7, 2023 at 1:45 PM gongzhongqiang <
> gongzhongqi...@apache.org
> wrote:
>
> It's very exciting to hear the news.
> +1 for adding CDC Connectors  to Apache Flink !
>
>
> Best,
> Zhongqiang
>
> Leonard Xu  于2023年12月7日周四 11:25写道：
>
> Dear Flink devs,
>
>
> As you may have heard, we at Alibaba (Ververica) are planning
> to
> donate
> CDC Connectors for the Apache Flink project
> *[1]* to the Apache Flink community.
>
>
>
> CDC Connectors for Apache Flink comprise a collection of source
> connectors designed specifically for Apache Flink. These
> connectors
> *[2]*
> enable the ingestion of changes from various databases using
> Change
> Data Capture (CDC), most of these CDC connectors are powered by
> Debezium
> *[3]*
> . They support both the DataStream API and the Table/SQL API,
> facilitating the reading of database snapshots and continuous
> reading
> of
> transaction logs with exactly-once processing, even in the
> event of
> failures.
>
>
> Additionally, in the latest version 3.0, we have introduced
> many
> long-awaited features. Starting from CDC version 3.0, we've
> built a
> Streaming ELT Framework available for streaming data
> integration.
> This
> framework allows users to write their data synchronization logic
> in a
> simple YAML file, which will automatically be translated into a
> Flink
> DataStreaming job. It emphasizes optimizing the task submission
> process
> and
> offers advanced functionalities such as whole database
> synchronization,
> merging sharded tables, and schema evolution
> *[4]*.
>
>
>
>
> I believe this initiative is a perfect match for both sides.
> For
> the
> Flink community, it presents an opportunity to enhance Flink's
> competitive
> advantage in streaming data integration, promoting the healthy
> growth
> and
> prosperity of the Apache Flink ecosystem. For the CDC Connectors
> project,
> becoming a sub-project of Apache Flink means being part of a
> neutral
> open-source community, which can attract a more diverse pool of
> contributors.
>
> Please note that the aforementioned points represent only some
> of
> our
> motivations and vision for this donation. Specific future
> operations
> need
> to be further discussed in this thread. For example, the
> sub-project
> name
> after the donation; we hope to name it Flink-CDC
> aiming to streaming data intergration through Apache Flink,
> following the naming convention of Flink-ML; And this project
> is
> managed
> by a total of 8 maintainers, including 3 Flink PMC members and 1
> Flink
> Committer. The remaining 4 maintainers are also highly active
> contributors
> to the Flink community, donating this project to the Flink
> community
> implies that their permissions might be reduced. Therefore, we
> may
> need
> to
> bring up this topic for 

Re: [DISCUSS] Remove legacy Paimon (TableStore) doc link from Flink web navigation

[Yu Li]

+1

Best Regards,
Yu


On Tue, 17 Oct 2023 at 18:59, Jing Ge  wrote:

> +1
>
> On Tue, Oct 17, 2023 at 11:13 AM Yong Fang  wrote:
>
> > +1
> >
> > On Tue, Oct 17, 2023 at 4:52 PM Leonard Xu  wrote:
> >
> > > +1
> > >
> > >
> > > > 2023年10月17日 下午4:50，Martijn Visser  写道：
> > > >
> > > > +1
> > > >
> > > > On Tue, Oct 17, 2023 at 10:34 AM Jingsong Li  >
> > > wrote:
> > > >>
> > > >> Hi marton,
> > > >>
> > > >> Thanks for driving. +1
> > > >>
> > > >> There is a PR to remove legacy Paimon
> > > >> https://github.com/apache/flink-web/pull/665 , but it hasn't been
> > > >> updated for a long time.
> > > >>
> > > >> Best,
> > > >> Jingsong
> > > >>
> > > >> On Tue, Oct 17, 2023 at 4:28 PM Márton Balassi  >
> > > wrote:
> > > >>>
> > > >>> Hi Flink & Paimon devs,
> > > >>>
> > > >>> The Flink webpage documentation navigation section still lists the
> > > outdated TableStore 0.3 and master docs as subproject docs (see
> > > attachment). I am all for advertising Paimon as a sister project of
> > Flink,
> > > but the current state is misleading in multiple ways.
> > > >>>
> > > >>> I would like to remove these obsolete links if the communities
> agree.
> > > >>>
> > > >>> Best,
> > > >>> Marton
> > >
> > >
> >
>

Re: [DISCUSS][2.0] FLIP-349: Move RocksDB statebackend classes to o.a.f.state.rocksdb package

[Yu Li]

+1

Best Regards,
Yu


On Wed, 26 Jul 2023 at 10:47, Yanfei Lei  wrote:

> +1 for moving all classes in the state-backend-rocksdb module under
> the classes to o.a.f.state.rocksdb package.
>
> I have always been curious about the relationship between
> o.a.f.contrib.xx and the flink-contrib module. :)
>
> Best,
> Yanfei
>
> Jing Ge  于2023年7月25日周二 17:50写道：
> >
> > make sense.
> >
> > Best regards,
> > Jing
> >
> > On Tue, Jul 25, 2023 at 4:29 PM Stefan Richter
> >  wrote:
> >
> > >
> > > +1
> > >
> > >
> > >
> > > > On 24. Jul 2023, at 12:25, Chesnay Schepler 
> wrote:
> > > >
> > > > To properly reflect the state of the rocksdb statebackend I propose
> to
> > > move all classes in the state-backend-rocksdb module under the classes
> to
> > > o.a.f.state.rocksdb package.
> > > >
> > > >
> > > >
> > >
> https://www.google.com/url?q=https://cwiki.apache.org/confluence/display/FLINK/FLIP-349%253A%2BMove%2BRocksDB%2Bstatebackend%2Bclasses%2Bto%2Bo.a.f.state.rocksdb%2Bpackage=gmail-imap=169079912800=AOvVaw3OiTwgsLEiTcJpNTVM-Y8y
> > >
> > >
>

Re: [VOTE] Release 2.0 must-have work items - Round 2

[Yu Li]

+1 (binding)

Thanks for driving this, Xintong!

Best Regards,
Yu


On Sun, 23 Jul 2023 at 18:28, Yuan Mei  wrote:

> +1 (binding)
>
> Thanks for driving the discussion through and for all the efforts in
> resolving the complexities :-)
>
> Best
> Yuan
>
> On Thu, Jul 20, 2023 at 5:23 PM Xintong Song 
> wrote:
>
> > Hi all,
> >
> > I'd like to start another round of VOTE for the must-have work items for
> > release 2.0 [1]. The corresponding discussion thread is [2], and the
> > previous voting thread is [3]. All comments from the previous voting
> thread
> > have been addressed.
> >
> > Please note that once the vote is approved, any changes to the must-have
> > items (adding / removing must-have items, changing the priority) requires
> > another vote. Assigning contributors / reviewers, updating descriptions /
> > progress, changes to nice-to-have items do not require another vote.
> >
> > The vote will be open until at least July 25, following the consensus
> > voting process. Votes of PMC members are binding.
> >
> > Best,
> >
> > Xintong
> >
> >
> > [1] https://cwiki.apache.org/confluence/display/FLINK/2.0+Release
> >
> > [2] https://lists.apache.org/thread/l3dkdypyrovd3txzodn07lgdwtwvhgk4
> >
> > [3] https://lists.apache.org/thread/r0y9syc6k5nmcxvnd0hj33htdpdj9k6m
> >
>

Re: Re: [ANNOUNCE] New Apache Flink Committer - Yong Fang

[Yu Li]

Congrats, Yong!

Best Regards,
Yu


On Tue, 25 Jul 2023 at 18:03, Sergey Nuyanzin  wrote:

> Congratulations, Yong Fang!
>
> On Tue, Jul 25, 2023 at 7:53 AM ConradJam  wrote:
>
> > Congratulations, Yong Fang
> >
> > Mang Zhang  于2023年7月25日周二 12:08写道：
> >
> > > Congratulations, Yong Fang!
> > >
> > >
> > > --
> > >
> > > Best regards,
> > > Mang Zhang
> > >
> > >
> > >
> > >
> > >
> > > 在 2023-07-25 10:30:24，"Jark Wu"  写道：
> > > >Congratulations, Yong Fang!
> > > >
> > > >Best,
> > > >Jark
> > > >
> > > >On Mon, 24 Jul 2023 at 22:11, Wencong Liu 
> wrote:
> > > >
> > > >> Congratulations!
> > > >>
> > > >> Best,
> > > >> Wencong Liu
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >> 在 2023-07-24 11:03:30，"Paul Lam"  写道：
> > > >> >Congrats, Shammon!
> > > >> >
> > > >> >Best,
> > > >> >Paul Lam
> > > >> >
> > > >> >> 2023年7月24日 10:56，Jingsong Li  写道：
> > > >> >>
> > > >> >> Shammon
> > > >> >
> > > >>
> > >
> >
> >
> > --
> > Best
> >
> > ConradJam
> >
>
>
> --
> Best regards,
> Sergey
>

Re: [VOTE] Release 2.0 must-have work items

[Yu Li]

4lhgt95zl4dzn168
> > >
> > > Best regards,
> > > Yuxia
> > >
> > > - 原始邮件 -
> > > 发件人: "Jing Ge" 
> > > 收件人: "dev" 
> > > 发送时间: 星期三, 2023年 7 月 12日 上午 1:23:40
> > > 主题: Re: [VOTE] Release 2.0 must-have work items
> > >
> > > agree with what Leonard said. There are actually more issues wrt the
> new
> > > Source and SinkV2[1]
> > >
> > > Speaking of must-have vs nice-to-have, I think it depends on the
> > priority.
> > > If removing them has higher priority, we should keep related tasks as
> > > must-have and make sure enough effort will be put to solve those issues
> > and
> > > therefore be able to remove those APIs.
> > >
> > > Best regards,
> > > Jing
> > >
> > > [1] https://lists.apache.org/thread/90qc9nrlzf0vbvg92klzp9ftxxc43nbk
> > >
> > > On Tue, Jul 11, 2023 at 10:26 AM Leonard Xu  wrote:
> > >
> > > > Thanks Xintong for driving this great work! But I’ve to give my
> > > > -1(binding) here：
> > > >
> > > > -1 to mark "deprecat SourceFunction/SinkFunction/Sinkv1" item as must
> > to
> > > > have for release 2.0.
> > > >
> > > > I do a lot of connector work in the community, and I have two
> insights
> > > > from past experience:
> > > >
> > > > 1. Many developers reported that it is very difficult to migrate from
> > > > SourceFunction to new Source [1]. The migration of existing
> conenctors
> > > > after deprecated SourceFunction is very difficult. Some developers
> > (Flavio
> > > > Pompermaier) reported that they gave up the migration because it was
> > too
> > > > complicated. I believe it's not a few cases. This means that
> > deprecating
> > > > SourceFunction related interfaces require community contributors to
> > reduce
> > > > the migration cost before starting the migration work.
> > > >
> > > > 2. IIRC, the function of SinkV2 cannot currently cover SinkFunction
> as
> > > > described in FLIP-287[2], it means the migration path after deprecate
> > > > SinkFunction/Sinkv1 does not exist, thus we cannot mark the related
> > > > interfaces of sinkfunction/sinkv1  as deprecated in 1.18.
> > > >
> > > > Based on these two cognitions, I think we should not mark these
> > interfaces
> > > > as must to have in 2.0. Maintaining the two sets of source/sink
> > interfaces
> > > > is not a concern for me, users can choose the interface to implement
> > > > according to their energy and needs.
> > > >
> > > > Btw, some work items in 2.0 are marked as must to have, but no
> > contributor
> > > > has claimed them yet. I think this is a risk and hope the Release
> > Managers
> > > > could pay attention to it.
> > > >
> > > > Thank you all RMs for your work, sorry again for interrupting the
> vote
> > > >
> > > > Best,
> > > > Leonard
> > > >
> > > > [1] https://lists.apache.org/thread/sqq26s9rorynr4vx4nhxz3fmmxpgtdqp
> > > > [2]
> > > >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=240880853
> > > >
> > > > > On Jul 11, 2023, at 4:11 PM, Yuan Mei 
> > wrote:
> > > > >
> > > > > As a second thought, I think "Eager State Declaration" is probably
> > not a
> > > > > must-have.
> > > > >
> > > > > I was originally thinking it is a prerequisite for "state querying
> > for
> > > > > disaggregated state management".
> > > > >
> > > > > Since disaggregated state management itself is not a must-have,
> > "Eager
> > > > > State Declaration" is not as well. We can downgrade it to "nice to
> > have"
> > > > if
> > > > > no objection.
> > > > >
> > > > > Best
> > > > >
> > > > > Yuan
> > > > >
> > > > > On Mon, Jul 10, 2023 at 7:02 PM Jing Ge  >
> > > > wrote:
> > > > >
> > > > >> +1
> > > > >>
> > > > >> On Mon, Jul 10, 2023 at 12:52 PM Yu Li  wrote:
> > > > >>
> > > > >>> +1 (binding)
> > > > >>>
> > > > >>> Thanks for driving this and great to see us moving forward.
> > > > >>>
> > > > >>> Best Regards,
> > > > >>> Yu
> > > > >>>
> > > > >>>
> > > > >>> On Mon, 10 Jul 2023 at 11:59, Feng Wang 
> > wrote:
> > > > >>>
> > > > >>>> +1
> > > > >>>> Thanks for driving this, looking forward to the next stage of
> > flink.
> > > > >>>>
> > > > >>>> On Fri, Jul 7, 2023 at 5:31 PM Xintong Song <
> > tonysong...@gmail.com>
> > > > >>> wrote:
> > > > >>>>
> > > > >>>>> Hi all,
> > > > >>>>>
> > > > >>>>> I'd like to start the VOTE for the must-have work items for
> > release
> > > > >> 2.0
> > > > >>>>> [1]. The corresponding discussion thread is [2].
> > > > >>>>>
> > > > >>>>> Please note that once the vote is approved, any changes to the
> > > > >>> must-have
> > > > >>>>> items (adding / removing must-have items, changing the
> priority)
> > > > >>> requires
> > > > >>>>> another vote. Assigning contributors / reviewers, updating
> > > > >>> descriptions /
> > > > >>>>> progress, changes to nice-to-have items do not require another
> > vote.
> > > > >>>>>
> > > > >>>>> The vote will be open until at least July 12, following the
> > consensus
> > > > >>>>> voting process. Votes of PMC members are binding.
> > > > >>>>>
> > > > >>>>> Best,
> > > > >>>>>
> > > > >>>>> Xintong
> > > > >>>>>
> > > > >>>>>
> > > > >>>>> [1]
> > https://cwiki.apache.org/confluence/display/FLINK/2.0+Release
> > > > >>>>>
> > > > >>>>> [2]
> > https://lists.apache.org/thread/l3dkdypyrovd3txzodn07lgdwtwvhgk4
> > > > >>>>>
> > > > >>>>
> > > > >>>
> > > > >>
> > > >
> > > >
> >
>

Re: [VOTE] Release 2.0 must-have work items

[Yu Li]

+1 (binding)

Thanks for driving this and great to see us moving forward.

Best Regards,
Yu


On Mon, 10 Jul 2023 at 11:59, Feng Wang  wrote:

> +1
> Thanks for driving this, looking forward to the next stage of flink.
>
> On Fri, Jul 7, 2023 at 5:31 PM Xintong Song  wrote:
>
> > Hi all,
> >
> > I'd like to start the VOTE for the must-have work items for release 2.0
> > [1]. The corresponding discussion thread is [2].
> >
> > Please note that once the vote is approved, any changes to the must-have
> > items (adding / removing must-have items, changing the priority) requires
> > another vote. Assigning contributors / reviewers, updating descriptions /
> > progress, changes to nice-to-have items do not require another vote.
> >
> > The vote will be open until at least July 12, following the consensus
> > voting process. Votes of PMC members are binding.
> >
> > Best,
> >
> > Xintong
> >
> >
> > [1] https://cwiki.apache.org/confluence/display/FLINK/2.0+Release
> >
> > [2] https://lists.apache.org/thread/l3dkdypyrovd3txzodn07lgdwtwvhgk4
> >
>

Re: [VOTE] FLIP-306: Unified File Merging Mechanism for Checkpoints

[Yu Li]

+1 (binding)

Thanks Zakelly for driving this, and thanks everyone for the thorough
discussion.

On Wed, May 10, 2023 at 11:15 AM Rui Fan <1996fan...@gmail.com> wrote:

> Thanks for driving this proposal, Zakelly.
>
> +1(binding)
>
> Best,
> Rui Fan
>
> On Wed, May 10, 2023 at 11:04 AM Hangxiang Yu  wrote:
>
> > Hi Zakelly.
> > Thanks for driving this.
> > +1 (no-binding)
> >
> > On Wed, May 10, 2023 at 10:52 AM Yuan Mei 
> wrote:
> >
> > > Thanks for driving this, Zakelly.
> > >
> > > As discussed in the thread,
> > >
> > > +1 for the proposal (binding)
> > >
> > > Best,
> > >
> > > Yuan
> > >
> > >
> > >
> > > On Wed, May 10, 2023 at 10:39 AM Zakelly Lan 
> > > wrote:
> > >
> > > > Hi everyone,
> > > >
> > > > Sorry for the 4 duplicate emails. There was a problem with the dev
> > > > mailing list blocking the mails from Gmail. I thought it was a
> network
> > > > problem so I tried several times. The issue is addressed by
> > > > INFRA-24572[1] and the piled up mails are delivered at one time.
> > > >
> > > > Based on the sending time, the vote will be open until May 12th at
> > > > 11:00PM GMT. Please discuss and vote in the last thread (this one).
> > > > Thanks!
> > > >
> > > >
> > > > Best regards,
> > > > Zakelly
> > > >
> > > > [1] https://issues.apache.org/jira/browse/INFRA-24572
> > > >
> > > > On Wed, May 10, 2023 at 10:30 AM Yanfei Lei 
> > wrote:
> > > > >
> > > > > +1 (no-binding)
> > > > >
> > > > > Best,
> > > > > Yanfei
> > > > >
> > > > >
> > > > > Jing Ge  于2023年5月10日周三 07:03写道：
> > > > >
> > > > > >
> > > > > > Hi Zakelly,
> > > > > >
> > > > > > I saw you sent at least 4 same emails for voting FLIP-306. I
> guess
> > > > this one
> > > > > > should be the last one and the right one for us to vote right?
> BTW,
> > > > based
> > > > > > on the sending time, 72 hours means to open the discussion until
> > May
> > > > 12th.
> > > > > >
> > > > > > Best regards,
> > > > > > Jing
> > > > > >
> > > > > > On Tue, May 9, 2023 at 8:24 PM Zakelly Lan <
> zakelly@gmail.com>
> > > > wrote:
> > > > > >
> > > > > > > Hi everyone,
> > > > > > >
> > > > > > > Thanks for all the feedback for FLIP-306: Unified File Merging
> > > > > > > Mechanism for Checkpoints[1] on the discussion thread[2].
> > > > > > >
> > > > > > > I'd like to start a vote for it. The vote will be open for at
> > least
> > > > 72
> > > > > > > hours (until May 11th, 12:00AM GMT) unless there is an
> objection
> > or
> > > > an
> > > > > > > insufficient number of votes.
> > > > > > >
> > > > > > >
> > > > > > > Best,
> > > > > > > Zakelly
> > > > > > >
> > > > > > > [1]
> > > > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-306%3A+Unified+File+Merging+Mechanism+for+Checkpoints
> > > > > > > [2]
> > > https://lists.apache.org/thread/56px3kvn3tlwpc7sl12kx6notfmk9g7q
> > > > > > >
> > > >
> > >
> >
> >
> > --
> > Best,
> > Hangxiang.
> >
>
-- 
Best Regards,
Yu

Re: [DISCUSS] Releasing Flink ML 2.2.0

[Yu Li]

+1. Great to know the (exciting) progress and thanks for the efforts!

Best Regards,
Yu


On Fri, 31 Mar 2023 at 14:39, Fan Hong  wrote:

> Hi Dong and Zhipeng,
>
> Thanks for starting the discussion. Glad to see a new release of Flink ML.
>
> Cheers!
>
> On Fri, Mar 31, 2023 at 2:34 PM Zhipeng Zhang 
> wrote:
>
> > Hi Dong,
> >
> > Thanks for starting the discussion. +1 for the Flink ML 2.1.0 release.
> >
>

[ANNOUNCE] Flink Table Store Joins Apache Incubator as Apache Paimon(incubating)

[Yu Li]

Dear Flinkers,


As you may have noticed, we are pleased to announce that Flink Table
Store has joined the Apache Incubator as a separate project called
Apache Paimon(incubating) [1] [2] [3]. The new project still aims at
building a streaming data lake platform for high-speed data ingestion,
change data tracking and efficient real-time analytics, with the
vision of supporting a larger ecosystem and establishing a vibrant and
neutral open source community.


We would like to thank everyone for their great support and efforts
for the Flink Table Store project, and warmly welcome everyone to join
the development and activities of the new project. Apache Flink will
continue to be one of the first-class citizens supported by Paimon,
and we believe that the Flink and Paimon communities will maintain
close cooperation.


亲爱的Flinkers，


正如您可能已经注意到的，我们很高兴地宣布，Flink Table Store 已经正式加入 Apache
孵化器独立孵化 [1] [2] [3]。新项目的名字是
Apache 
Paimon(incubating)，仍致力于打造一个支持高速数据摄入、流式数据订阅和高效实时分析的新一代流式湖仓平台。此外，新项目将支持更加丰富的生态，并建立一个充满活力和中立的开源社区。


在这里我们要感谢大家对 Flink Table Store 项目的大力支持和投入，并热烈欢迎大家加入新项目的开发和社区活动。Apache Flink
将继续作为 Paimon 支持的主力计算引擎之一，我们也相信 Flink 和 Paimon 社区将继续保持密切合作。


Best Regards,

Yu (on behalf of the Apache Flink PMC and Apache Paimon PPMC)


致礼，

李钰（谨代表 Apache Flink PMC 和 Apache Paimon PPMC）


[1] https://paimon.apache.org/

[2] https://github.com/apache/incubator-paimon

[3] https://cwiki.apache.org/confluence/display/INCUBATOR/PaimonProposal

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

[Yu Li]

+1 (binding)


- Checked the diff between 1.15.3 and 1.15.4-rc1: *OK* (
https://github.com/apache/flink/compare/release-1.15.3...release-1.15.4-rc1)

  - AWS SDKv2 version has been bumped to 2.19.14 through FLINK-30633 and
all NOTICE files updated correctly

- Checked release notes: *OK*

- Checked sums and signatures: *OK*

- Maven clean install from source: *OK* (8u181)

- Checked the jars in the staging repo: *OK*

- Checked the website updates: *OK*


Thanks for driving this release, Danny!


Best Regards,
Yu


On Wed, 1 Mar 2023 at 02:01, Ahmed Hamdy  wrote:

> Thanks Danny,
>
> +1 (non-binding)
>
> - Verified hashes and signatures
> - Built Source archive using maven
> - Web PR looks good.
> - Started WordCount Example
>
> On Tue, 28 Feb 2023 at 16:37, Jing Ge  wrote:
>
> > Thanks Danny,
> >
> > +1 (non-binding)
> >
> >  - GPG signatures looks good
> >  - checked dist and maven repo
> >  - maven clean install from source
> >  - checked version consistency in pom files
> >  - went through the web release notes and found one task is still open:
> > FLINK-31133 [1]
> >  - download artifacts
> >  - started/stopped local cluster and ran WordCount job in streaming and
> > batch
> >
> > Best regards,
> > Jing
> >
> > [1] https://issues.apache.org/jira/browse/FLINK-31133
> >
> > On Tue, Feb 28, 2023 at 3:12 PM Matthias Pohl
> >  wrote:
> >
> > > Thanks Danny.
> > >
> > > +1 (non-binding)
> > >
> > > * Downloaded artifacts
> > > * Built Flink from sources
> > > * Verified SHA512 checksums GPG signatures
> > > * Compared checkout with provided sources
> > > * Verified pom file versions
> > > * Went over NOTICE file/pom files changes without finding anything
> > > suspicious
> > > * Deployed standalone session cluster and ran WordCount example in
> batch
> > > and streaming: Nothing suspicious in log files found
> > >
> > > On Tue, Feb 28, 2023 at 9:50 AM Teoh, Hong
>  > >
> > > wrote:
> > >
> > > > Thanks Danny for driving this
> > > >
> > > > +1 (non-binding)
> > > >
> > > > * Hashes and Signatures look good
> > > > * All required files on dist.apache.org
> > > > * Source archive builds using maven
> > > > * Started packaged example WordCountSQLExample job
> > > > * Web PR looks good.
> > > >
> > > > Cheers,
> > > > Hong
> > > >
> > > >
> > > >
> > > > > On 24 Feb 2023, at 05:36, Weihua Hu 
> wrote:
> > > > >
> > > > > CAUTION: This email originated from outside of the organization. Do
> > not
> > > > click links or open attachments unless you can confirm the sender and
> > > know
> > > > the content is safe.
> > > > >
> > > > >
> > > > >
> > > > > Thanks Danny.
> > > > >
> > > > > +1(non-binding)
> > > > >
> > > > > Tested the following:
> > > > > - Download the artifacts and build image
> > > > > - Ran WordCount on Kubernetes(session mode and application mode)
> > > > >
> > > > >
> > > > > Best,
> > > > > Weihua
> > > > >
> > > > >
> > > > > On Fri, Feb 24, 2023 at 12:29 PM Yanfei Lei 
> > > wrote:
> > > > >
> > > > >> Thanks Danny.
> > > > >> +1 (non-binding)
> > > > >>
> > > > >> - Downloaded artifacts & built Flink from sources
> > > > >> - Verified GPG signatures of bin and source.
> > > > >> - Verified version in poms
> > > > >> - Ran WordCount example in streaming and batch mode(standalone
> > > cluster)
> > > > >> - Went over flink-web PR, looks good except for Sergey's remark.
> > > > >>
> > > > >> Danny Cranmer  于2023年2月24日周五 02:08写道：
> > > > >>>
> > > > >>> Hi everyone,
> > > > >>> Please review and vote on the release candidate #1 for the
> version
> > > > >> 1.15.4,
> > > > >>> as follows:
> > > > >>> [ ] +1, Approve the release
> > > > >>> [ ] -1, Do not approve the release (please provide specific
> > comments)
> > > > >>>
> > > > >>>
> > > > >>> The complete staging area is available for your review, which
> > > includes:
> > > > >>> * JIRA release notes [1],
> > > > >>> * the official Apache source release and binary convenience
> > releases
> > > to
> > > > >> be
> > > > >>> deployed to dist.apache.org [2], which are signed with the key
> > with
> > > > >>> fingerprint 125FD8DB [3],
> > > > >>> * all artifacts to be deployed to the Maven Central Repository
> [4],
> > > > >>> * source code tag "release-1.15.4-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 (excluding weekends
> > > > >> 2023-02-28
> > > > >>> 19:00). It is adopted by majority approval, with at least 3 PMC
> > > > >> affirmative
> > > > >>> votes.
> > > > >>>
> > > > >>> Thanks,
> > > > >>> Danny
> > > > >>>
> > > > >>> [1]
> > > > >>>
> > > > >>
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12352526
> > > > >>> [2]
> https://dist.apache.org/repos/dist/dev/flink/flink-1.15.4-rc1/
> > > > >>> [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> > > > >>> [4]
> > > > >>>
> > > > >>
> > > >
> > >
> >
> 

Re: [VOTE] Flink minor version support policy for old releases

[Yu Li]

+1 (binding)

Best Regards,
Yu


On Thu, 2 Mar 2023 at 09:53, Jark Wu  wrote:

> +1 (binding)
>
> Best,
> Jark
>
> > 2023年3月2日 05:03，Gyula Fóra  写道：
> >
> > +1 (binding)
> >
> > Gyula
> >
> > On Wed, Mar 1, 2023 at 9:57 PM Thomas Weise  wrote:
> >
> >> +1 (binding)
> >>
> >> Thanks,
> >> Thomas
> >>
> >> On Tue, Feb 28, 2023 at 6:53 AM Sergey Nuyanzin 
> >> wrote:
> >>
> >>> +1 (non-binding)
> >>>
> >>> Thanks for driving this Danny.
> >>>
> >>> On Tue, Feb 28, 2023 at 9:41 AM Samrat Deb 
> >> wrote:
> >>>
>  +1 (non binding)
> 
>  Thanks for driving it
> 
>  Bests,
>  Samrat
> 
>  On Tue, 28 Feb 2023 at 1:36 PM, Junrui Lee 
> >> wrote:
> 
> > Thanks Danny for driving it.
> >
> > +1 (non-binding)
> >
> > Best regards,
> > Junrui
> >
> > yuxia  于2023年2月28日周二 14:04写道：
> >
> >> Thanks Danny for driving it.
> >>
> >> +1 (non-binding)
> >>
> >> Best regards,
> >> Yuxia
> >>
> >> - 原始邮件 -
> >> 发件人: "Weihua Hu" 
> >> 收件人: "dev" 
> >> 发送时间: 星期二, 2023年 2 月 28日 下午 12:48:09
> >> 主题: Re: [VOTE] Flink minor version support policy for old releases
> >>
> >> Thanks, Danny.
> >>
> >> +1 (non-binding)
> >>
> >> Best,
> >> Weihua
> >>
> >>
> >> On Tue, Feb 28, 2023 at 12:38 PM weijie guo <
> >>> guoweijieres...@gmail.com
> >
> >> wrote:
> >>
> >>> Thanks Danny for bring this.
> >>>
> >>> +1 (non-binding)
> >>>
> >>> Best regards,
> >>>
> >>> Weijie
> >>>
> >>>
> >>> Jing Ge  于2023年2月27日周一 20:23写道：
> >>>
>  +1 (non-binding)
> 
>  BTW, should we follow the content style [1] to describe the new
>  rule
> >>> using
>  1.2.x, 1.1.y, 1.1.z?
> 
>  [1]
> > https://flink.apache.org/downloads/#update-policy-for-old-releases
> 
>  Best regards,
>  Jing
> 
>  On Mon, Feb 27, 2023 at 1:06 PM Matthias Pohl
>   wrote:
> 
> > Thanks, Danny. Sounds good to me.
> >
> > +1 (non-binding)
> >
> > On Wed, Feb 22, 2023 at 10:11 AM Danny Cranmer <
> >>> dannycran...@apache.org>
> > wrote:
> >
> >> I am starting a vote to update the "Update Policy for old
> > releases"
> >>> [1]
> > to
> >> include additional bugfix support for end of life versions.
> >>
> >> As per the discussion thread [2], the change we are voting
> >> on
>  is:
> >> - Support policy: updated to include: "Upon release of a
> >> new
> > Flink
>  minor
> >> version, the community will perform one final bugfix
> >> release
>  for
>  resolved
> >> critical/blocker issues in the Flink minor version losing
> > support."
> >> - Release process: add a step to start the discussion
> >> thread
>  for
> >> the
> > final
> >> patch version, if there are resolved critical/blocking
> >> issues
>  to
> >>> flush.
> >>
> >> Voting schema: since our bylaws [3] do not cover this
>  particular
> > scenario,
> >> and releases require PMC involvement, we will use a
> >> consensus
> > vote
> >>> with
> > PMC
> >> binding votes.
> >>
> >> Thanks,
> >> Danny
> >>
> >> [1]
> >
> >>
> >>> https://flink.apache.org/downloads.html#update-policy-for-old-releases
> >> [2]
> >> https://lists.apache.org/thread/szq23kr3rlkm80rw7k9n95js5vqpsnbv
> >> [3]
> > https://cwiki.apache.org/confluence/display/FLINK/Flink+Bylaws
> >>
> >
> 
> >>>
> >>
> >
> 
> >>>
> >>>
> >>> --
> >>> Best regards,
> >>> Sergey
> >>>
> >>
>
>

Re: [VOTE] Apache Flink Table Store 0.3.0, release candidate #1

[Yu Li]

Thanks for the quick action Jingsong! Here is my vote with the new staging
directory:

+1 (binding)


- Checked release notes: *Action Required*

  * The fix version of FLINK-30620 and FLINK-30628 are 0.3.0 but still
open, please confirm whether this should be included or we should move it
out of 0.3.0

- Checked sums and signatures: *OK*

- Checked the jars in the staging repo: *OK*

- Checked source distribution doesn't include binaries: *OK*

- Maven clean install from source: *OK*

- Checked version consistency in pom files: *OK*

- Went through the quick start: *OK*

  * Verified with flink 1.14.6, 1.15.3 and 1.16.0

- Checked the website updates: *OK*

Best Regards,
Yu


On Thu, 12 Jan 2023 at 15:36, Jingsong Li  wrote:

> Thanks Yu for your validation.
>
> I created a new staging directory [1]
>
> [1]
> https://repository.apache.org/content/repositories/orgapacheflink-1577/
>
> Best,
> Jingsong
>
> On Thu, Jan 12, 2023 at 3:07 PM Yu Li  wrote:
> >
> > Hi Jingsong,
> >
> > It seems the given staging directory [1] is not exposed, could you double
> > check and republish if necessary? Thanks.
> >
> > Best Regards,
> > Yu
> >
> > [1]
> https://repository.apache.org/content/repositories/orgapacheflink-1576/
> >
> >
> > On Tue, 10 Jan 2023 at 16:53, Jingsong Li 
> wrote:
> >
> > > Hi everyone,
> > >
> > > Please review and vote on the release candidate #1 for the version
> > > 0.3.0 of Apache Flink Table Store, as follows:
> > >
> > > [ ] +1, Approve the release
> > > [ ] -1, Do not approve the release (please provide specific comments)
> > >
> > > **Release Overview**
> > >
> > > As an overview, the release consists of the following:
> > > a) Table Store canonical source distribution to be deployed to the
> > > release repository at dist.apache.org
> > > b) Table Store binary convenience releases to be deployed to the
> > > release repository at dist.apache.org
> > > c) Maven artifacts to be deployed to the Maven Central Repository
> > >
> > > **Staging Areas to Review**
> > >
> > > The staging areas containing the above mentioned artifacts are as
> follows,
> > > for your review:
> > > * All artifacts for a) and b) can be found in the corresponding dev
> > > repository at dist.apache.org [2]
> > > * All artifacts for c) can be found at the Apache Nexus Repository [3]
> > >
> > > All artifacts are signed with the key
> > > 2C2B6A653B07086B65E4369F7C76245E0A318150 [4]
> > >
> > > Other links for your review:
> > > * JIRA release notes [5]
> > > * source code tag "release-0.3.0-rc1" [6]
> > > * PR to update the website Downloads page to include Table Store links
> [7]
> > >
> > > **Vote Duration**
> > >
> > > The voting time will run for at least 72 hours.
> > > It is adopted by majority approval, with at least 3 PMC affirmative
> votes.
> > >
> > > Best,
> > > Jingsong Lee
> > >
> > > [1]
> > >
> https://cwiki.apache.org/confluence/display/FLINK/Verifying+a+Flink+Table+Store+Release
> > > [2]
> > >
> https://dist.apache.org/repos/dist/dev/flink/flink-table-store-0.3.0-rc1/
> > > [3]
> > >
> https://repository.apache.org/content/repositories/orgapacheflink-1576/
> > > [4] https://dist.apache.org/repos/dist/release/flink/KEYS
> > > [5]
> > >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12352111
> > > [6] https://github.com/apache/flink-table-store/tree/release-0.3.0-rc1
> > > [7] https://github.com/apache/flink-web/pull/601
> > >
>

Re: [VOTE] Apache Flink Table Store 0.3.0, release candidate #1

[Yu Li]

Hi Jingsong,

It seems the given staging directory [1] is not exposed, could you double
check and republish if necessary? Thanks.

Best Regards,
Yu

[1] https://repository.apache.org/content/repositories/orgapacheflink-1576/


On Tue, 10 Jan 2023 at 16:53, Jingsong Li  wrote:

> Hi everyone,
>
> Please review and vote on the release candidate #1 for the version
> 0.3.0 of Apache Flink Table Store, as follows:
>
> [ ] +1, Approve the release
> [ ] -1, Do not approve the release (please provide specific comments)
>
> **Release Overview**
>
> As an overview, the release consists of the following:
> a) Table Store canonical source distribution to be deployed to the
> release repository at dist.apache.org
> b) Table Store binary convenience releases to be deployed to the
> release repository at dist.apache.org
> c) Maven artifacts to be deployed to the Maven Central Repository
>
> **Staging Areas to Review**
>
> The staging areas containing the above mentioned artifacts are as follows,
> for your review:
> * All artifacts for a) and b) can be found in the corresponding dev
> repository at dist.apache.org [2]
> * All artifacts for c) can be found at the Apache Nexus Repository [3]
>
> All artifacts are signed with the key
> 2C2B6A653B07086B65E4369F7C76245E0A318150 [4]
>
> Other links for your review:
> * JIRA release notes [5]
> * source code tag "release-0.3.0-rc1" [6]
> * PR to update the website Downloads page to include Table Store links [7]
>
> **Vote Duration**
>
> The voting time will run for at least 72 hours.
> It is adopted by majority approval, with at least 3 PMC affirmative votes.
>
> Best,
> Jingsong Lee
>
> [1]
> https://cwiki.apache.org/confluence/display/FLINK/Verifying+a+Flink+Table+Store+Release
> [2]
> https://dist.apache.org/repos/dist/dev/flink/flink-table-store-0.3.0-rc1/
> [3]
> https://repository.apache.org/content/repositories/orgapacheflink-1576/
> [4] https://dist.apache.org/repos/dist/release/flink/KEYS
> [5]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12352111
> [6] https://github.com/apache/flink-table-store/tree/release-0.3.0-rc1
> [7] https://github.com/apache/flink-web/pull/601
>

Re: [ANNOUNCE] New Apache Flink Committer - Lincoln Lee

[Yu Li]

Congratulations, Lincoln!

Best Regards,
Yu


On Wed, 11 Jan 2023 at 21:17, Martijn Visser 
wrote:

> Congratulations Lincoln, happy to have you on board!
>
> Best regards, Martijn
>
>
> On Wed, Jan 11, 2023 at 1:49 PM Dong Lin  wrote:
>
> > Congratulations, Lincoln!
> >
> > Cheers,
> > Dong
> >
> > On Tue, Jan 10, 2023 at 11:52 AM Jark Wu  wrote:
> >
> > > Hi everyone,
> > >
> > > On behalf of the PMC, I'm very happy to announce Lincoln Lee as a new
> > Flink
> > > committer.
> > >
> > > Lincoln Lee has been a long-term Flink contributor since 2017. He
> mainly
> > > works on Flink
> > > SQL parts and drives several important FLIPs, e.g., FLIP-232 (Retry
> Async
> > > I/O), FLIP-234 (
> > > Retryable Lookup Join), FLIP-260 (TableFunction Finish). Besides, He
> also
> > > contributed
> > > much to Streaming Semantics, including the non-determinism problem and
> > the
> > > message
> > > ordering problem.
> > >
> > > Please join me in congratulating Lincoln for becoming a Flink
> committer!
> > >
> > > Cheers,
> > > Jark Wu
> > >
> >
>

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

[Yu Li]

+1 for the proposal (extending the 1.17 feature freeze date to Jan 31st).

Best Regards,
Yu


On Tue, 3 Jan 2023 at 15:11, Zhu Zhu  wrote:

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

Re: [DISCUSS] Release new FRocksDB

[Yu Li]

+1 to have a new FRocksDB release. Thanks Yanfei and all for the efforts!

Best Regards,
Yu


On Fri, 16 Dec 2022 at 17:02, Martijn Visser 
wrote:

> Hi Yanfei,
>
> Big +1 for adding ARM support. It would be great to be able to get tests to
> pass on Mac M1s.
>
> Best regards,
>
> Martijn
>
> On Mon, Dec 12, 2022 at 3:37 PM Márton Balassi 
> wrote:
>
> > Hi Yanfei,
> >
> > Makes sense, arm architecture support would be great. Thanks for looking
> > into this.
> >
> > On Mon, Dec 12, 2022 at 3:03 PM Yanfei Lei  wrote:
> >
> > > Hi devs,
> > >
> > > I'd like to bring up a discussion about releasing the new frocksdbjni
> > > version,  we are planning to adapt frocksdbjni to Apple M1 machines in
> > > Flink 1.17[1], a new frocksdbjni jar needs to be released.
> > >
> > > Thanks to the efforts of the community, FLINK-24932[1] has been merged
> > into
> > > FRocksDB-6.20.3 branch, and many thanks to *Ververica* for providing a
> > paid
> > > CircleCI for testing, which ensures the correctness of the code.
> > >
> > > The new frocksdbjni version is still based on 6.20.3[2], the code
> > > interfaces and performance[3] will not change. In addition to
> > > FLINK-24932[1],  some fixes of vulnerabilities[4] will also be included
> > in
> > > the new version, see FLINK-30321[5].
> > >
> > > Are there any minor fixes you would like to include in this release?
> > > Welcome to create PR for FrocksDB[6].
> > > Looking forward to your opinions.
> > >
> > > [1] https://issues.apache.org/jira/browse/FLINK-24932
> > > [2]
> > >
> > >
> >
> https://mvnrepository.com/artifact/com.ververica/frocksdbjni/6.20.3-ververica-1.0
> > > [3]
> > >
> > >
> >
> https://issues.apache.org/jira/browse/FLINK-24932?focusedCommentId=17569889=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17569889
> > > [4] https://lists.apache.org/thread/rm40f45qfw6rls70k35o2dt0k4tz9bsr
> > > [5] https://issues.apache.org/jira/browse/FLINK-30321
> > > [6] https://github.com/ververica/frocksdb
> > >
> > > --
> > > Best,
> > > Yanfei
> > >
> >
>

Re: [VOTE] FLIP-263: Improve resolving schema compatibility

[Yu Li]

+1 (binding)

Thanks Hangxiang for driving this and thanks all for the thorough
discussion.

Best Regards,
Yu


On Fri, 28 Oct 2022 at 16:01, Dawid Wysakowicz 
wrote:

> +1,
>
> Best,
>
> Dawid
>
> On 28/10/2022 08:08, godfrey he wrote:
> > +1 (binding)
> >
> > Thanks for driving this!
> >
> > Best,
> > Godfrey
> >
> > Yun Gao  于2022年10月28日周五 13:50写道：
> >> +1 (binding)
> >>
> >> Thanks Hangxiang for driving the FLIP.
> >>
> >> Best,
> >> Yun Gao
> >>
> >>
> >>
> >>
> >>   --Original Mail --
> >> Sender:Zakelly Lan 
> >> Send Date:Fri Oct 28 12:27:01 2022
> >> Recipients:Flink Dev 
> >> Subject:Re: [VOTE] FLIP-263: Improve resolving schema compatibility
> >> Hi Hangxiang,
> >>
> >> The current plan looks good to me, +1 (non-binding). Thanks for driving
> this.
> >>
> >> Best,
> >> Zakelly
> >>
> >> On Fri, Oct 28, 2022 at 11:18 AM Yuan Mei 
> wrote:
> >>> +1 (binding)
> >>>
> >>> Thanks for driving this.
> >>>
> >>> Best
> >>> Yuan
> >>>
> >>> On Fri, Oct 28, 2022 at 11:17 AM yanfei lei 
> wrote:
> >>>
>  +1(non-binding) and thanks for Hangxiang's driving.
> 
> 
> 
>  Hangxiang Yu  于2022年10月28日周五 09:24写道：
> 
> > Hi everyone,
> >
> > I'd like to start the vote for FLIP-263 [1].
> >
> > Thanks for your feedback and the discussion in [2][3].
> >
> > The vote will be open for at least 72 hours.
> >
> > Best regards,
> > Hangxiang.
> >
> > [1]
> >
> >
> 
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-263%3A+Improve+resolving+schema+compatibility
> > [2] https://lists.apache.org/thread/4w36oof8dh28b9f593sgtk21o8qh8qx4
> >
> > [3] https://lists.apache.org/thread/t0bdkx1161rlbnsf06x0kswb05mch164
> >
> 
>  --
>  Best,
>  Yanfei
> 
>

Re: [DISCUSS] Planning Flink 1.17

[Yu Li]

+1 to feature freeze the 1.17 release on 1.17 (smile), and thanks all for
volunteering as our release managers.

Looking forward to the soon-released 1.16.0 and the detailed feature plan
for 1.17.

Best Regards,
Yu


On Fri, 21 Oct 2022 at 20:17, Jing Ge  wrote:

> +1
> The plan looks rational. Thanks for your effort!
>
> Best regards,
> Jing
>
> On Fri, Oct 21, 2022 at 1:16 PM Congxian Qiu 
> wrote:
>
> > Thanks for kicking off the 1.17 release, and volunteers as release
> > managers.
> >
> > +1 to the feature freeze date
> >
> > Best,
> > Congxian
> >
> >
> > Yun Tang  于2022年10月21日周五 17:24写道：
> >
> > > Thanks, Qingsheng and Leonard to kick off the release plan of
> flink-1.17,
> > > which targets a feature freeze date of January 17th .
> > >
> > > +1 to include Martijn and Matthias as the release managers.
> > >
> > > Best,
> > > Yun Tang
> > > 
> > > From: Piotr Nowojski 
> > > Sent: Friday, October 21, 2022 16:22
> > > To: dev@flink.apache.org 
> > > Subject: Re: [DISCUSS] Planning Flink 1.17
> > >
> > > Hi,
> > >
> > > Thanks for kicking this discussion off Qingsheng and Leonard. I like
> the
> > > January 17th, 2023 touch :)
> > >
> > > 1 for including Matthias Pohl and Martijn Visser as release managers.
> > >
> > > Best,
> > > Piotrek
> > > Always alright
> > >
> > > pt., 21 paź 2022 o 05:55 Yuan Mei  napisał(a):
> > >
> > > > Thanks, Qingsheng for the kicking-off efforts.
> > > >
> > > > 1. January 17th, 2023 as feature freeze data sounds reasonable to me.
> > > > 2. We will input our plan to the wiki link.
> > > >
> > > > Thanks
> > > >
> > > > Best
> > > > Yuan
> > > > Ververica (Alibaba)
> > > >
> > > >
> > > > On Fri, Oct 21, 2022 at 10:38 AM Xingbo Huang 
> wrote:
> > > >
> > > > > Thanks Qingsheng, Leonard and Martijn for starting the discussion
> and
> > > > > volunteering.
> > > > > The timeline proposal sounds reasonable :+1:
> > > > >
> > > > > Best,
> > > > > Xingbo
> > > > >
> > > > > Jark Wu  于2022年10月21日周五 00:17写道：
> > > > >
> > > > > > Thanks for kicking off the 1.17 release.
> > > > > >
> > > > > > Targeting feature freeze on 1/17 for 1.17 release sounds pretty
> > good
> > > to
> > > > > me.
> > > > > > +1 for the volunteers as release managers.
> > > > > >
> > > > > > Best,
> > > > > > Jark
> > > > > > Ververica (Alibaba)
> > > > > >
> > > > > > On Thu, 20 Oct 2022 at 18:09, Matthias Pohl <
> > matthias.p...@aiven.io
> > > > > > .invalid>
> > > > > > wrote:
> > > > > >
> > > > > > > Thanks for starting the discussion about Flink 1.17. I would be
> > > > > > interested
> > > > > > > in helping out around the release as well.
> > > > > > >
> > > > > > > Best,
> > > > > > > Matthias
> > > > > > >
> > > > > > > On Thu, Oct 20, 2022 at 12:07 PM Xintong Song <
> > > tonysong...@gmail.com
> > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Thanks for kicking this off.
> > > > > > > >
> > > > > > > > +1 for the proposed timeline.
> > > > > > > >
> > > > > > > > Also +1 for Qingsheng, Leonard and Martijn as the release
> > > managers.
> > > > > > > Thanks
> > > > > > > > for volunteering.
> > > > > > > >
> > > > > > > > Best,
> > > > > > > >
> > > > > > > > Xintong
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On Thu, Oct 20, 2022 at 3:59 PM Martijn Visser <
> > > > > > martijnvis...@apache.org
> > > > > > > >
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Hi Qingsheng,
> > > > > > > > >
> > > > > > > > > I'm definitely interested in participating as a release
> > manager
> > > > > > again.
> > > > > > > > >
> > > > > > > > > Best regards,
> > > > > > > > >
> > > > > > > > > Martijn
> > > > > > > > >
> > > > > > > > > On Thu, Oct 20, 2022 at 9:47 AM Qingsheng Ren <
> > > re...@apache.org>
> > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Hi everyone,
> > > > > > > > > >
> > > > > > > > > > As we are approaching the official release of Flink 1.16,
> > > it’s
> > > > a
> > > > > > good
> > > > > > > > > time
> > > > > > > > > > to kick off some discussions and march toward 1.17.
> > > > > > > > > >
> > > > > > > > > > - Release managers
> > > > > > > > > >
> > > > > > > > > > Leonard Xu and I would like to volunteer as release
> > managers
> > > > for
> > > > > > > 1.17,
> > > > > > > > > and
> > > > > > > > > > it would be great to have someone else working together
> on
> > > this
> > > > > > > > release.
> > > > > > > > > > Please let us know if you have any interest!
> > > > > > > > > >
> > > > > > > > > > - Timeline
> > > > > > > > > >
> > > > > > > > > > Having 1.16 will be released in the next few days and
> the 4
> > > > > months
> > > > > > > > > release
> > > > > > > > > > cycle after that, we propose to set the feature freezing
> > date
> > > > on
> > > > > > > > *January
> > > > > > > > > > 17th, 2023* (aligned with our version number 1.17 :-)),
> so
> > > that
> > > > > > > > everyone
> > > > > > > > > > could enjoy the holiday season and Chinese new year.
> > > > > > > > > >
> > > > > > > > > > - 

Re: [VOTE] Drop Gelly

[Yu Li]

+1

Thanks for the clarification Martijn and Yun. Hopefully we can document
somewhere that there is a plan (maybe long term) to introduce a replacement
based on the new iteration framework introduced in flink-ml (based on
DataStream API) after dropping the old Gelly library, and let our users
know that they could either use the old one, or join the community efforts
to build up the new one.

Personally I hope that we are not delivering a message that Flink won't
support graph processing anymore, unless this is exactly what we mean.

Best Regards,
Yu


On Thu, 13 Oct 2022 at 21:42, Maximilian Michels  wrote:

> +1
>
> On Thu, Oct 13, 2022 at 12:00 PM Konstantin Knauf 
> wrote:
>
> > +1
> >
> > Am Do., 13. Okt. 2022 um 10:56 Uhr schrieb Niels Basjes  >:
> >
> > > +1
> > >
> > > On Wed, Oct 12, 2022 at 11:00 PM Martijn Visser <
> > martijnvis...@apache.org>
> > > wrote:
> > >
> > > > Hi everyone,
> > > >
> > > > I would like to open a vote for dropping Gelly, which was discussed a
> > > long
> > > > time ago but never put to a vote [1].
> > > >
> > > > Voting will be open for at least 72 hours.
> > > >
> > > > Best regards,
> > > >
> > > > Martijn
> > > > https://twitter.com/MartijnVisser82
> > > > https://github.com/MartijnVisser
> > > >
> > > > [1] https://lists.apache.org/thread/2m6wtgjvxcogbf9d5q7mqt4ofqjf2ojc
> > > >
> > >
> > >
> > > --
> > > Best regards / Met vriendelijke groeten,
> > >
> > > Niels Basjes
> > >
> >
> >
> > --
> > https://twitter.com/snntrable
> > https://github.com/knaufk
> >
>

Re: [VOTE] Drop Gelly

[Yu Li]

Hi Martijn,

>From the last replies of the previous discussion, I could see there are
still users using Gelly that expressed their wish to somehow keep this
module [1] [2] [3]. Therefore, Before giving my vote, I'd like to
confirm what "Drop Gelly" exactly means. Does it mean that 1) we remove the
codes and documents of Gelly completely, or 2) just move it out of the main
repository into a separate one and mark it as EOM (or maybe call for
maintainers), or 3) something else? And if the #1 option, is there any
replacement (or any plan)? Thanks.

Best Regards,
Yu

[1] https://lists.apache.org/thread/4yxb7xnb2070h5lypcd3wxnsck9zwz8f
[2] https://lists.apache.org/thread/x21p382vjt6nrjnj51fxxtcrp1dqtzyz
[3] https://lists.apache.org/thread/w2f4yvb75tg5t7g3l7t9z6bvpwmd1t6y


On Thu, 13 Oct 2022 at 10:56, Yun Gao  wrote:

> +1
> Best,
> Yun Gao
> --
> From:Martijn Visser 
> Send Time:2022 Oct. 13 (Thu.) 04:59
> To:dev 
> Subject:[VOTE] Drop Gelly
> Hi everyone,
> I would like to open a vote for dropping Gelly, which was discussed a long
> time ago but never put to a vote [1].
> Voting will be open for at least 72 hours.
> Best regards,
> Martijn
> https://twitter.com/MartijnVisser82
> https://github.com/MartijnVisser
> [1] https://lists.apache.org/thread/2m6wtgjvxcogbf9d5q7mqt4ofqjf2ojc
>

Re: [VOTE] Apache Flink Table Store 0.2.1, release candidate #2

[Yu Li]

+1 (binding)

- Checked release notes: *Action Required*
  * The fix version of FLINK-29554 is 0.2.1 but still open, please confirm
whether this should be included or we should move it out of 0.2.1
- Checked sums and signatures: *OK*
- Checked the jars in the staging repo: *OK*
- Checked source distribution doesn't include binaries: *OK*
- Maven clean install from source: *OK*
- Checked version consistency in pom files: *OK*
- Went through the quick start: *OK*
  * Verified with both flink 1.14.5 and 1.15.1
- Checked the website updates: *OK*
  * Minor: left some comments in the PR, please check

Thanks for driving this release, Jingsong!

Best Regards,
Yu


On Sat, 8 Oct 2022 at 10:25, Jingsong Li  wrote:

> Hi everyone,
>
> Please review and vote on the release candidate #2 for the version
> 0.2.1 of Apache Flink Table Store, as follows:
>
> [ ] +1, Approve the release
> [ ] -1, Do not approve the release (please provide specific comments)
>
> **Release Overview**
>
> As an overview, the release consists of the following:
> a) Table Store canonical source distribution to be deployed to the
> release repository at dist.apache.org
> b) Table Store binary convenience releases to be deployed to the
> release repository at dist.apache.org
> c) Maven artifacts to be deployed to the Maven Central Repository
>
> **Staging Areas to Review**
>
> The staging areas containing the above mentioned artifacts are as follows,
> for your review:
> * All artifacts for a) and b) can be found in the corresponding dev
> repository at dist.apache.org [2]
> * All artifacts for c) can be found at the Apache Nexus Repository [3]
>
> All artifacts are signed with the key
> 2C2B6A653B07086B65E4369F7C76245E0A318150 [4]
>
> Other links for your review:
> * JIRA release notes [5]
> * source code tag "release-0.2.1-rc2" [6]
> * PR to update the website Downloads page to include Table Store links [7]
>
> **Vote Duration**
>
> The voting time will run for at least 72 hours.
> It is adopted by majority approval, with at least 3 PMC affirmative votes.
>
> Best,
> Jingsong Lee
>
> [1]
> https://cwiki.apache.org/confluence/display/FLINK/Verifying+a+Flink+Table+Store+Release
> [2]
> https://dist.apache.org/repos/dist/dev/flink/flink-table-store-0.2.1-rc2/
> [3]
> https://repository.apache.org/content/repositories/orgapacheflink-1539/
> [4] https://dist.apache.org/repos/dist/release/flink/KEYS
> [5]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12352257
> [6] https://github.com/apache/flink-table-store/tree/release-0.2.1-rc2
> [7] https://github.com/apache/flink-web/pull/571
>

Re: [VOTE] FLIP-254 Redis Streams connector

[Yu Li]

+1 (binding)

Thanks for the clarification Martijn. I'd suggest considering adding a note
in the FLIP document (since the proposed repository name for this connector
is "flink-connector-redis") or changing the repository name to
"flink-connector-redis-streams".

Best Regards,
Yu


On Thu, 15 Sept 2022 at 20:45, Martijn Visser 
wrote:

> Hi Ryan and Yu,
>
> > There's quite a bit of existing code and it looks like there's
> > interest and community willing to contribute to this connector with 2
> > implementations already in the flink-connector-redis repo[1].
>
> Yes, this FLIP is to formalize that the Flink community wants to add this
> connector from that repository. We shouldn't have created the repo without
> having an accepted FLIP first :)
>
> > There's a couple of points that should probably be fixed in the FLIP
>
> Very good catch, I've updated the ones that you've mentioned.
>
> > does this FLIP only aim to add source/sink connectors for
> > Redis Streams, and we will create another one to support
> > regular Redis data structures (as LookupTableSource or Sink)?
>
> The scope of this FLIP is limited to adding a source/sink connector for
> Redis Streams. Things like LookupTableSource can be considered in the
> future.
>
> Best regards,
>
> Martijn
>
> Op di 13 sep. 2022 om 07:02 schreef Yu Li :
>
> > Hi Martijn,
> >
> > Thanks for driving this forward, but from the discussion thread [1], it
> > seems one question from Konstantin is still not answered: does this FLIP
> > only aim to add source/sink connectors for Redis Streams, and we will
> > create another one to support regular Redis data structures (as
> > LookupTableSource or Sink)? I think it's necessary to confirm the scope
> of
> > the FLIP before voting (smile).
> >
> > Best Regards,
> > Yu
> >
> > [1] https://lists.apache.org/thread/9pftp3x10602nzr9c0ln4h9zt8hg2rjk
> >
> >
> > On Mon, 12 Sept 2022 at 22:05, Ryan Skraba  >
> > wrote:
> >
> > > Hello!  There's quite a bit of existing code and it looks like there's
> > > interest and community willing to contribute to this connector with 2
> > > implementations already in the flink-connector-redis repo[1].
> > >
> > > There's a couple of points that should probably be fixed in the FLIP:
> > some
> > > typos such as "provide at-least guarantees" and the initial version
> > should
> > > not be 1.0.0 given that version 1.1.5 was already released in its
> > previous
> > > incarnation[2].
> > >
> > > In principle: +1 (non-binding)
> > >
> > > All my best, Ryan
> > >
> > > [1]: https://github.com/apache/flink-connector-redis/pulls
> > > [2]:
> > >
> >
> https://mvnrepository.com/artifact/org.apache.flink/flink-connector-redis
> > >
> > >
> > >
> > > On Mon, Sep 12, 2022 at 10:20 AM Zheng Yu Chen 
> > > wrote:
> > >
> > > > +1 (non-binding)
> > > >
> > > > Martijn Visser  于2022年9月12日周一 15:58写道：
> > > >
> > > > > Hi everyone,
> > > > >
> > > > > With no comments provided in the discussion thread, I'm opening a
> > vote
> > > > > thread on FLIP-254: Redis Streams connector:
> > > > >
> > > > > FLIP:
> > > > >
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-254%3A+Redis+Streams+Connector
> > > > >
> > > > >
> > > > > The vote will be open for at least 72h.
> > > > >
> > > > > Best regards,
> > > > >
> > > > > Martijn
> > > > > https://twitter.com/MartijnVisser82
> > > > > https://github.com/MartijnVisser
> > > > >
> > > >
> > >
> >
>

Re: [VOTE] FLIP-254 Redis Streams connector

[Yu Li]

Hi Martijn,

Thanks for driving this forward, but from the discussion thread [1], it
seems one question from Konstantin is still not answered: does this FLIP
only aim to add source/sink connectors for Redis Streams, and we will
create another one to support regular Redis data structures (as
LookupTableSource or Sink)? I think it's necessary to confirm the scope of
the FLIP before voting (smile).

Best Regards,
Yu

[1] https://lists.apache.org/thread/9pftp3x10602nzr9c0ln4h9zt8hg2rjk


On Mon, 12 Sept 2022 at 22:05, Ryan Skraba 
wrote:

> Hello!  There's quite a bit of existing code and it looks like there's
> interest and community willing to contribute to this connector with 2
> implementations already in the flink-connector-redis repo[1].
>
> There's a couple of points that should probably be fixed in the FLIP: some
> typos such as "provide at-least guarantees" and the initial version should
> not be 1.0.0 given that version 1.1.5 was already released in its previous
> incarnation[2].
>
> In principle: +1 (non-binding)
>
> All my best, Ryan
>
> [1]: https://github.com/apache/flink-connector-redis/pulls
> [2]:
> https://mvnrepository.com/artifact/org.apache.flink/flink-connector-redis
>
>
>
> On Mon, Sep 12, 2022 at 10:20 AM Zheng Yu Chen 
> wrote:
>
> > +1 (non-binding)
> >
> > Martijn Visser  于2022年9月12日周一 15:58写道：
> >
> > > Hi everyone,
> > >
> > > With no comments provided in the discussion thread, I'm opening a vote
> > > thread on FLIP-254: Redis Streams connector:
> > >
> > > FLIP:
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-254%3A+Redis+Streams+Connector
> > >
> > >
> > > The vote will be open for at least 72h.
> > >
> > > Best regards,
> > >
> > > Martijn
> > > https://twitter.com/MartijnVisser82
> > > https://github.com/MartijnVisser
> > >
> >
>

Re: [DISCUSS] Releasing Flink 1.14.6

[Yu Li]

+1

Best Regards,
Yu


On Tue, 6 Sept 2022 at 17:57, Xintong Song  wrote:

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

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

[Yu Li]

+1

Thanks for the efforts, Chesnay

Best Regards,
Yu


On Tue, 6 Sept 2022 at 18:17, Martijn Visser 
wrote:

> +1 (binding)
>
> Op di 6 sep. 2022 om 11:59 schreef Xingbo Huang :
>
> > Thanks Chesnay for driving this,
> >
> > +1
> >
> > Best,
> > Xingbo
> >
> > Xintong Song  于2022年9月6日周二 17:57写道：
> >
> > > +1
> > >
> > > Best,
> > >
> > > Xintong
> > >
> > >
> > >
> > > On Tue, Sep 6, 2022 at 5:55 PM Konstantin Knauf 
> > wrote:
> > >
> > > > +1. Thanks, Chesnay.
> > > >
> > > > Am Di., 6. Sept. 2022 um 11:51 Uhr schrieb Chesnay Schepler <
> > > > ches...@apache.org>:
> > > >
> > > > > Since no one objected in the discuss thread, let's vote!
> > > > >
> > > > > FLIP:
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=225152857
> > > > >
> > > > > The vote will be open for at least 72h.
> > > > >
> > > > > Regards,
> > > > > Chesnay
> > > > >
> > > >
> > > >
> > > > --
> > > > https://twitter.com/snntrable
> > > > https://github.com/knaufk
> > > >
> > >
> >
>

Re: [DISCUSS] FLIP-254 Guarantee binary compatibility for Public/-Evolving APIs between patch releases

[Yu Li]

Thanks for the follow-up Chesnay, I believe this compatible result is
useful, and +1 for applying the FLIP to 1.15.

And yes, from the result we are doing a good job keeping the binary
compatibility in the 1.15 branch :-)

Best Regards,
Yu


On Thu, 1 Sept 2022 at 19:54, Chesnay Schepler  wrote:

> I compared 1.15.0 and 1.15.2; we overall did a very good job with one
> outlier.
> Based on this I'd say we should also apply this FLIP to 1.15.
>
> Table connectors:
> Source-compatible change; relevant if you implement your own
> DataStream(Scan/Sink)Provider:
>
>   
> org.apache.flink.table.connector.sink.DataStreamSinkProvider.consumeDataStream(org.apache.flink.table.connector.ProviderContext,org.apache.flink.streaming.api.datastream.DataStream):METHOD_ABSTRACT_NOW_DEFAULT
>
>   
> org.apache.flink.table.connector.source.DataStreamScanProvider.produceDataStream(org.apache.flink.table.connector.ProviderContext,org.apache.flink.streaming.api.environment.StreamExecutionEnvironment):METHOD_ABSTRACT_NOW_DEFAULT
>
> Pulsar connector:
> These are due to adding @Internal in 1.15.2; no effect on compatibility:
>
> org.apache.flink.connector.pulsar.source.enumerator.cursor.CursorPosition.getMessageId():METHOD_REMOVED
>
> org.apache.flink.connector.pulsar.source.enumerator.cursor.CursorPosition$Type.valueOf(java.lang.String):METHOD_REMOVED
>
> org.apache.flink.connector.pulsar.source.enumerator.cursor.CursorPosition$Type.values():METHOD_REMOVED,java.lang.Comparable[java.lang.Comparable]:INTERFACE_REMOVED,java.io.Serializable[
> java.io.Serializable]:INTERFACE_REMOVED
>
> org.apache.flink.connector.pulsar.source.enumerator.cursor.CursorPosition$Type:SUPERCLASS_REMOVED
>
> org.apache.flink.connector.pulsar.source.enumerator.cursor.CursorPosition$Type.TIMESTAMP:FIELD_REMOVED
>
> org.apache.flink.connector.pulsar.source.enumerator.cursor.CursorPosition$Type.MESSAGE_ID:FIELD_REMOVED
>
> org.apache.flink.connector.pulsar.source.enumerator.cursor.CursorPosition$Type:CLASS_REMOVED
> These are straight-up breaking changes (neither source nor binary
> compatible):
>
> org.apache.flink.connector.pulsar.source.enumerator.cursor.CursorPosition.seekPosition(org.apache.pulsar.client.api.Consumer):METHOD_REMOVED
>
> org.apache.flink.connector.pulsar.source.enumerator.cursor.StartCursor.fromPublishTime(long):METHOD_NEW_DEFAULT
>
> org.apache.flink.connector.pulsar.source.enumerator.cursor.StartCursor.seekPosition(java.lang.String,int,org.apache.pulsar.client.api.Consumer):METHOD_REMOVED
>
> org.apache.flink.connector.pulsar.source.enumerator.cursor.StopCursor.afterEventTime(long):METHOD_NEW_DEFAULT,org.apache.flink.connector.pulsar.source.enumerator.cursor.StopCursor.afterPublishTime(long):METHOD_NEW_DEFAULT
>
> org.apache.flink.connector.pulsar.source.enumerator.cursor.StopCursor.shouldStop(org.apache.pulsar.client.api.Message):METHOD_RETURN_TYPE_CHANGED
>
>
> On 01/09/2022 03:49, Yu Li wrote:
> > *bq. a list of all breaking changes between 1.15.0 and the latest 1.15.x
> > (or intermediate releases)*
> > Yes, this might help users to be more prepared before upgrading, if they
> > could know whether need to recompile their applications. Asking about
> > 1.14/1.15 since they are the "in service" versions.
> >
> > But it's totally fine if we're targeting for the future (smile).
> >
> > Best Regards,
> > Yu
> >
> >
> > On Wed, 31 Aug 2022 at 21:41, Chesnay Schepler 
> wrote:
> >
> >> Well then someone didnt update the FLIP number as they should!
> >> I'll increment the number of this FLIP to 255.
> >>
> >> On 31/08/2022 15:06, Matthias Pohl wrote:
> >>> +1 for bringing this into a consistent state. Thanks, Chesnay.
> >>>
> >>> nit: There's a conflict between this FLIP-254 and the FLIP-254 on the
> >> redis
> >>> streams connector.
> >>>
> >>> On Wed, Aug 31, 2022 at 2:52 PM Chesnay Schepler 
> >> wrote:
> >>>> * backport to 1.14/1.15
> >>>>
> >>>> On 31/08/2022 14:45, Chesnay Schepler wrote:
> >>>>> @Yu I haven't really considered 1.14/1.15.
> >>>>>
> >>>>> What exactly are you interested in; a list of all breaking changes
> >>>>> between 1.15.0 and the latest 1.15.x (or intermediate releases),
> >>>>> or are you suggesting to also backport this whole thing to 1.16
> (which
> >>>>> should be possible)?
> >>>>>
> >>>>> On 31/08/2022 13:31, Yu Li wrote:
> >>>>>> +1 for the FLIP. Thanks for the efforts Chesnay.
> >>>>>>
> >>>>>> I bel

Re: [DISCUSS] FLIP-254 Guarantee binary compatibility for Public/-Evolving APIs between patch releases

[Yu Li]

*bq. a list of all breaking changes between 1.15.0 and the latest 1.15.x
(or intermediate releases)*
Yes, this might help users to be more prepared before upgrading, if they
could know whether need to recompile their applications. Asking about
1.14/1.15 since they are the "in service" versions.

But it's totally fine if we're targeting for the future (smile).

Best Regards,
Yu


On Wed, 31 Aug 2022 at 21:41, Chesnay Schepler  wrote:

> Well then someone didnt update the FLIP number as they should!
> I'll increment the number of this FLIP to 255.
>
> On 31/08/2022 15:06, Matthias Pohl wrote:
> > +1 for bringing this into a consistent state. Thanks, Chesnay.
> >
> > nit: There's a conflict between this FLIP-254 and the FLIP-254 on the
> redis
> > streams connector.
> >
> > On Wed, Aug 31, 2022 at 2:52 PM Chesnay Schepler 
> wrote:
> >
> >> * backport to 1.14/1.15
> >>
> >> On 31/08/2022 14:45, Chesnay Schepler wrote:
> >>> @Yu I haven't really considered 1.14/1.15.
> >>>
> >>> What exactly are you interested in; a list of all breaking changes
> >>> between 1.15.0 and the latest 1.15.x (or intermediate releases),
> >>> or are you suggesting to also backport this whole thing to 1.16 (which
> >>> should be possible)?
> >>>
> >>> On 31/08/2022 13:31, Yu Li wrote:
> >>>> +1 for the FLIP. Thanks for the efforts Chesnay.
> >>>>
> >>>> I believe ensuring binary compatibility for patch releases will also
> >>>> benefit our end users besides the cloud service providers.
> >>>>
> >>>> I'm also wondering about the compatibility checking result after
> >>>> enabling
> >>>> japicmp for all modules with existing patch releases (1.14.x and
> >>>> 1.15.x).
> >>>> Do you already have one with your local customized japicmp or do we
> >>>> need to
> >>>> wait until the works tracked in JIRA are done? (smile)
> >>>>
> >>>> Best Regards,
> >>>> Yu
> >>>>
> >>>>
> >>>> On Wed, 31 Aug 2022 at 18:50, Konstantin Knauf 
> >>>> wrote:
> >>>>
> >>>>> Hi Chesnay,
> >>>>>
> >>>>> thanks for bringing this up and for your research and fixes to
> japicmd.
> >>>>>
> >>>>> +1 for the proposal. For Immerok as an Apache Flink cloud service
> >>>>> provider
> >>>>> it is very valuable to know that our users don't need to upgrade
> >>>>> their Jobs
> >>>>> when the Flink patch version changes. I am sure the same is true for
> >>>>> internal platform teams as well as end users of Apache Flink.
> >>>>>
> >>>>> Cheers,
> >>>>>
> >>>>> Konstantin
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> Am Mi., 31. Aug. 2022 um 12:31 Uhr schrieb Chesnay Schepler <
> >>>>> ches...@apache.org>:
> >>>>>
> >>>>>> Hello,
> >>>>>>
> >>>>>> I just published a FLIP to guarantee binary compatibility for patch
> >>>>>> releases. I don't think our current guarantees of
> source-compatibility
> >>>>>> are sufficient for patch releases.
> >>>>>>
> >>>>>>
> >>
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=225152857
> >>>>>> Let me know what you think.
> >>>>>>
> >>>>>> Regards,
> >>>>>> Chesnay
> >>>>>>
> >>>>> --
> >>>>> https://twitter.com/snntrable
> >>>>> https://github.com/knaufk
> >>>>>
> >>
>
>

Re: [DISCUSS] FLIP-254 Guarantee binary compatibility for Public/-Evolving APIs between patch releases

[Yu Li]

+1 for the FLIP. Thanks for the efforts Chesnay.

I believe ensuring binary compatibility for patch releases will also
benefit our end users besides the cloud service providers.

I'm also wondering about the compatibility checking result after enabling
japicmp for all modules with existing patch releases (1.14.x and 1.15.x).
Do you already have one with your local customized japicmp or do we need to
wait until the works tracked in JIRA are done? (smile)

Best Regards,
Yu


On Wed, 31 Aug 2022 at 18:50, Konstantin Knauf  wrote:

> Hi Chesnay,
>
> thanks for bringing this up and for your research and fixes to japicmd.
>
> +1 for the proposal. For Immerok as an Apache Flink cloud service provider
> it is very valuable to know that our users don't need to upgrade their Jobs
> when the Flink patch version changes. I am sure the same is true for
> internal platform teams as well as end users of Apache Flink.
>
> Cheers,
>
> Konstantin
>
>
>
>
>
> Am Mi., 31. Aug. 2022 um 12:31 Uhr schrieb Chesnay Schepler <
> ches...@apache.org>:
>
> > Hello,
> >
> > I just published a FLIP to guarantee binary compatibility for patch
> > releases. I don't think our current guarantees of source-compatibility
> > are sufficient for patch releases.
> >
> >
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=225152857
> >
> > Let me know what you think.
> >
> > Regards,
> > Chesnay
> >
>
>
> --
> https://twitter.com/snntrable
> https://github.com/knaufk
>

Re: [VOTE] Apache Flink Table Store 0.2.0, release candidate #3

[Yu Li]

+1 (binding)

- Checked release notes: *OK*
- Checked sums and signatures: *OK*
- Checked the jars in the staging repo: *OK*
- Checked source distribution doesn't include binaries: *OK*
- Maven clean install from source: *OK*
- Checked version consistency in pom files: *OK*
- Went through the quick start: *OK*
  * Verified with both flink 1.14.5 and 1.15.1
- Checked the website updates: *OK*

Thanks all for the efforts!

Best Regards,
Yu


On Wed, 24 Aug 2022 at 19:24, Nicholas Jiang 
wrote:

> Hi all!
>
> +1 for the release (non-binding). I've verified the jar with SQL client
> and listed the check items as follows:
>
> * Compiled the sources and built the source distribution - PASSED
> * Ran through Quick Start Guide - PASSED
> * Checked Spark 2.3.4&3.3.0 reader and catalog with table store jar -
> PASSED
> * Checked all NOTICE files - PASSED
> * Checked the website updates - PASSED
>
> Regards,
> Nicholas Jiang
>
> On 2022/08/24 07:46:00 Jingsong Li wrote:
> > Hi everyone,
> >
> > Please review and vote on the release candidate #3 for the version 0.2.0
> of
> > Apache Flink Table Store, as follows:
> >
> > [ ] +1, Approve the release
> > [ ] -1, Do not approve the release (please provide specific comments)
> >
> > **Release Overview**
> >
> > As an overview, the release consists of the following:
> > a) Table Store canonical source distribution to be deployed to the
> > release repository at dist.apache.org
> > b) Table Store binary convenience releases to be deployed to the
> > release repository at dist.apache.org
> > c) Maven artifacts to be deployed to the Maven Central Repository
> >
> > **Staging Areas to Review**
> >
> > The staging areas containing the above mentioned artifacts are as
> follows,
> > for your review:
> > * All artifacts for a) and b) can be found in the corresponding dev
> > repository at dist.apache.org [2]
> > * All artifacts for c) can be found at the Apache Nexus Repository [3]
> >
> > All artifacts are signed with the key
> > 2C2B6A653B07086B65E4369F7C76245E0A318150 [4]
> >
> > Other links for your review:
> > * JIRA release notes [5]
> > * source code tag "release-0.2.0-rc3" [6]
> > * PR to update the website Downloads page to include Table Store links
> [7]
> >
> > **Vote Duration**
> >
> > The voting time will run for at least 72 hours.
> > It is adopted by majority approval, with at least 3 PMC affirmative
> votes.
> >
> > Best,
> > Jingsong Lee
> >
> > [1]
> https://cwiki.apache.org/confluence/display/FLINK/Verifying+a+Flink+Table+Store+Release
> > [2]
> https://dist.apache.org/repos/dist/dev/flink/flink-table-store-0.2.0-rc3/
> > [3]
> https://repository.apache.org/content/repositories/orgapacheflink-1526/
> > [4] https://dist.apache.org/repos/dist/release/flink/KEYS
> > [5]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12351570
> > [6] https://github.com/apache/flink-table-store/tree/release-0.2.0-rc3
> > [7] https://github.com/apache/flink-web/pull/562
> >
>

Re: Re: [ANNOUNCE] New Apache Flink Committer - Junhan Yang

[Yu Li]

Congratulations, Junhan!

Best Regards,
Yu


On Thu, 25 Aug 2022 at 10:07, Yun Gao  wrote:

> Congratulations Junhan!
>
>
> Best,
> Yun Gao
>
>
> --
> Sender:Yangze Guo
> Date:2022/08/25 10:04:14
> Recipient:dev
> Cc:
> Theme:Re: [ANNOUNCE] New Apache Flink Committer - Junhan Yang
>
> Congrats!
>
> Jark Wu  于 2022年8月24日周三 下午3:46写道：
>
> > Congrats Junhan!
> >
> > Best,
> > Jark
> >
> > On Wed, 24 Aug 2022 at 15:05, Qingsheng Ren  wrote:
> >
> > > Congratulations Junhan!
> > >
> > > Best regards,
> > > Qingsheng
> > >
> > > > On Aug 22, 2022, at 16:30, Yang Wang  wrote:
> > > >
> > > > Congrats Junhan!
> > > >
> > > >
> > > > Best,
> > > > Yang
> > > >
> > > > Matthias Pohl  于2022年8月22日周一
> 15:35写道：
> > > >
> > > >> Congratulations & welcome! :-)
> > > >>
> > > >> Matthias
> > > >>
> > > >> On Sun, Aug 21, 2022 at 5:42 AM Yuan Mei 
> > > wrote:
> > > >>
> > > >>> Congratulations Junhan!
> > > >>>
> > > >>> Best,
> > > >>> Yuan
> > > >>>
> > > >>> On Sat, Aug 20, 2022 at 2:11 PM Danny Cranmer <
> > dannycran...@apache.org
> > > >
> > > >>> wrote:
> > > >>>
> > >  Congratulations Junhan! Welcome to the team.
> > > 
> > >  On Sat, 20 Aug 2022, 03:01 yuxia, 
> > > wrote:
> > > 
> > > > Congratulations, Junhan!
> > > >
> > > > Best regards,
> > > > Yuxia
> > > >
> > > > - 原始邮件 -
> > > > 发件人: "Aitozi" 
> > > > 收件人: "dev" 
> > > > 发送时间: 星期六, 2022年 8 月 20日 上午 12:18:29
> > > > 主题: Re: [ANNOUNCE] New Apache Flink Committer - Junhan Yang
> > > >
> > > > Congratulations, Junhan!
> > > > Best,
> > > > Aitozi
> > > >
> > > > Guowei Ma  于2022年8月19日周五 13:18写道：
> > > >
> > > >> Congratulations, Junhan!
> > > >> Best,
> > > >> Guowei
> > > >>
> > > >>
> > > >> On Fri, Aug 19, 2022 at 6:01 AM Jing Ge 
> > > >> wrote:
> > > >>
> > > >>> Congrats Junhan!
> > > >>>
> > > >>> Best regards,
> > > >>> Jing
> > > >>>
> > > >>> On Thu, Aug 18, 2022 at 12:05 PM Jark Wu 
> > > >> wrote:
> > > >>>
> > >  Congrats and welcome Junhan!
> > > 
> > >  Cheers,
> > >  Jark
> > > 
> > > > 2022年8月18日 17:59，Timo Walther  写道：
> > > >
> > > > Congratulations and welcome to the committer team :-)
> > > >
> > > > Regards,
> > > > Timo
> > > >
> > > > On 18.08.22 07:19, Lijie Wang wrote:
> > > >> Congratulations, Junhan!
> > > >> Best,
> > > >> Lijie
> > > >> Leonard Xu  于2022年8月18日周四 11:31写道：
> > > >>> Congratulations, Junhan!
> > > >>>
> > > >>> Best,
> > > >>>
> > >  2022年8月18日 上午11:27，Zhipeng Zhang  > > >>>
> > >  写道：
> > > 
> > >  Congratulations, Junhan!
> > > 
> > >  Xintong Song  于2022年8月18日周四 11:21写道：
> > > >
> > > > Hi everyone,
> > > >
> > > > On behalf of the PMC, I'm very happy to announce Junhan
> > > >>> Yang
> > > > as a
> > > >>> new
> > > >>> Flink
> > > > committer.
> > > >
> > > > Junhan has been contributing to the Flink project for
> > > >> more
> > > > than 1
> > >  year.
> > > >>> His
> > > > contributions are mostly identified in the web frontend,
> > > >> including
> > > > FLIP-241, FLIP-249 and various maintenance efforts of
> > > >>> Flink's
> > >  frontend
> > > > frameworks.
> > > >
> > > > Please join me in congratulating Junhan for becoming a
> > > >>> Flink
> > >  committer!
> > > >
> > > > Best,
> > > > Xintong
> > > 
> > > 
> > > 
> > >  --
> > >  best,
> > >  Zhipeng
> > > >>>
> > > >>>
> > > >
> > > 
> > > 
> > > >>>
> > > >>
> > > >
> > > 
> > > >>>
> > > >>
> > >
> > >
> >
>
>

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

[Yu Li]

Congratulations, Lijie!

Best Regards,
Yu


On Thu, 25 Aug 2022 at 10:07, Yun Gao  wrote:

> Congratulations Lijie!
>
> Best,
> Yun Gao
>
>
> --
> Sender:Yangze Guo
> Date:2022/08/25 10:04:35
> Recipient:dev
> Cc:Lijie Wang
> Theme:Re: [ANNOUNCE] New Apache Flink Committer - Lijie Wang
>
> Congrats!
>
> Jark Wu  于 2022年8月24日周三 下午3:47写道：
>
> > Congrats Lijie!
> >
> > Best,
> > Jark
> >
> > On Wed, 24 Aug 2022 at 15:06, Qingsheng Ren  wrote:
> >
> > > Congratulations Lijie!
> > >
> > > Best regards,
> > > Qingsheng
> > >
> > > > On Aug 22, 2022, at 16:29, Yang Wang  wrote:
> > > >
> > > > Congrats Lijie!
> > > >
> > > > Best,
> > > > Yang
> > > >
> > > > Matthias Pohl  于2022年8月22日周一
> 15:34写道：
> > > >
> > > >> Congrats & welcome to the team! :-)
> > > >>
> > > >> Matthias
> > > >>
> > > >> On Sun, Aug 21, 2022 at 5:41 AM Yuan Mei 
> > > wrote:
> > > >>
> > > >>> Congratulations, Lijie!
> > > >>>
> > > >>> Best,
> > > >>> Yuan
> > > >>>
> > > >>> On Sat, Aug 20, 2022 at 2:12 PM Danny Cranmer <
> > dannycran...@apache.org
> > > >
> > > >>> wrote:
> > > >>>
> > >  Congratulations Lijie! Welcome to the team.
> > > 
> > >  On Sat, 20 Aug 2022, 03:25 Yun Tang,  wrote:
> > > 
> > > > Congratulations, Lijie!
> > > >
> > > >
> > > > Best
> > > > Yun Tang
> > > > 
> > > > From: Geng Biao 
> > > > Sent: Saturday, August 20, 2022 10:03
> > > > To: dev@flink.apache.org 
> > > > Subject: Re: [ANNOUNCE] New Apache Flink Committer - Lijie Wang
> > > >
> > > > Congratulations Lijie!
> > > > Best,
> > > > Biao Geng
> > > >
> > > > 获取 Outlook for iOS
> > > > 
> > > > 发件人: yuxia 
> > > > 发送时间: Saturday, August 20, 2022 9:54:29 AM
> > > > 收件人: dev 
> > > > 主题: Re: [ANNOUNCE] New Apache Flink Committer - Lijie Wang
> > > >
> > > > Congrats Lijie!
> > > >
> > > > Best regards,
> > > > Yuxia
> > > >
> > > > - 原始邮件 -
> > > > 发件人: "Aitozi" 
> > > > 收件人: "dev" 
> > > > 发送时间: 星期六, 2022年 8 月 20日 上午 12:19:27
> > > > 主题: Re: [ANNOUNCE] New Apache Flink Committer - Lijie Wang
> > > >
> > > > Congrats Lijie!
> > > >
> > > > Best regards,
> > > > Aitozi
> > > >
> > > > Jing Ge  于2022年8月19日周五 06:02写道：
> > > >
> > > >> Congrats Lijie!
> > > >>
> > > >> Best regards,
> > > >> Jing
> > > >>
> > > >> On Thu, Aug 18, 2022 at 8:40 AM Terry Wang 
> > > >>> wrote:
> > > >>
> > > >>> Congratulations, Lijie!
> > > >>>
> > > >>> On Thu, Aug 18, 2022 at 11:31 AM Leonard Xu  >
> > >  wrote:
> > > >>>
> > >  Congratulations, Lijie!
> > > 
> > >  Best,
> > >  Leonard
> > > 
> > > > 2022年8月18日 上午11:26，Zhipeng Zhang 
> > > >> 写道：
> > > >
> > > > Congratulations, Lijie!
> > > >
> > > > Xintong Song  于2022年8月18日周四 11:23写道：
> > > >>
> > > >> Congratulations Lijie, and welcome~!
> > > >>
> > > >> Best,
> > > >>
> > > >> Xintong
> > > >>
> > > >>
> > > >>
> > > >> On Thu, Aug 18, 2022 at 11:12 AM Xingbo Huang <
> > >  hxbks...@gmail.com
> > > >>
> > >  wrote:
> > > >>
> > > >>> Congrats, Lijie
> > > >>>
> > > >>> Best,
> > > >>> Xingbo
> > > >>>
> > > >>> Lincoln Lee  于2022年8月18日周四
> > > >> 11:01写道：
> > > >>>
> > >  Congratulations, Lijie!
> > > 
> > >  Best,
> > >  Lincoln Lee
> > > 
> > > 
> > >  Benchao Li  于2022年8月18日周四 10:51写道：
> > > 
> > > > Congratulations Lijie!
> > > >
> > > > yanfei lei  于2022年8月18日周四 10:44写道：
> > > >
> > > >> Congratulations, Lijie!
> > > >>
> > > >> Best,
> > > >> Yanfei
> > > >>
> > > >> JunRui Lee  于2022年8月18日周四 10:35写道：
> > > >>
> > > >>> Congratulations, Lijie!
> > > >>>
> > > >>> Best,
> > > >>> JunRui
> > > >>>
> > > >>> Timo Walther  于2022年8月17日周三
> > > >> 19:30写道：
> > > >>>
> > >  Congratulations and welcome to the committer team :-)
> > > 
> > >  Regards,
> > >  Timo
> > > 
> > > 
> > >  On 17.08.22 12:50, Yuxin Tan wrote:
> > > > Congratulations, Lijie!
> > > >
> > > > Best,
> > > > Yuxin
> > > >
> > > >
> > > > Guowei Ma  于2022年8月17日周三
> > > >>> 18:42写道：
> > > >
> > > 

Re: [VOTE] Apache Flink Table Store 0.2.0, release candidate #2

[Yu Li]

+1 (binding)

- Checked release notes: *Action Required*
  - Minor: there're still 25 open issues with fix version marked as 0.2.0
and need to be updated [1]
- Checked sums and signatures: *OK*
- Checked the jars in the staging repo: *OK*
- Checked source distribution doesn't include binaries: *OK*
- Maven clean install from source: *OK*
- Checked version consistency in pom files: *OK*
- Went through the quick start: *OK*
- Checked the website updates: *OK*
  - Minor: left some suggestions, please check.

Thanks for driving this release, Jingsong!

Best Regards,
Yu

[1]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20FLINK%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20fixVersion%20%3D%20table-store-0.2.0%20AND%20component%20%3D%20%22Table%20Store%22


On Thu, 18 Aug 2022 at 15:30, Nicholas Jiang 
wrote:

> Hi all!
>
> +1 for the release (non-binding). I've verified the jar with SQL client
> and listed the check items as follows:
>
> * Compiled the sources and built the source distribution - PASSED
> * Ran through Quick Start Guide - PASSED
> * Checked Spark 2.3.4&3.3.0 reader and catalog with table store jar -
> PASSED
> * Checked all NOTICE files - PASSED
>
> Regards,
> Nicholas Jiang
>
> On 2022/08/17 10:16:54 Jingsong Li wrote:
> > Hi everyone,
> >
> > Please review and vote on the release candidate #2 for the version 0.2.0
> of
> > Apache Flink Table Store, as follows:
> >
> > [ ] +1, Approve the release
> > [ ] -1, Do not approve the release (please provide specific comments)
> >
> > **Release Overview**
> >
> > As an overview, the release consists of the following:
> > a) Table Store canonical source distribution to be deployed to the
> > release repository at dist.apache.org
> > b) Table Store binary convenience releases to be deployed to the
> > release repository at dist.apache.org
> > c) Maven artifacts to be deployed to the Maven Central Repository
> >
> > **Staging Areas to Review**
> >
> > The staging areas containing the above mentioned artifacts are as
> follows,
> > for your review:
> > * All artifacts for a) and b) can be found in the corresponding dev
> > repository at dist.apache.org [2]
> > * All artifacts for c) can be found at the Apache Nexus Repository [3]
> >
> > All artifacts are signed with the key
> > 2C2B6A653B07086B65E4369F7C76245E0A318150 [4]
> >
> > Other links for your review:
> > * JIRA release notes [5]
> > * source code tag "release-0.2.0-rc2" [6]
> > * PR to update the website Downloads page to include Table Store links
> [7]
> >
> > **Vote Duration**
> >
> > The voting time will run for at least 72 hours.
> > It is adopted by majority approval, with at least 3 PMC affirmative
> votes.
> >
> > Best,
> > Jingsong Lee
> >
> > [1]
> https://cwiki.apache.org/confluence/display/FLINK/Verifying+a+Flink+Table+Store+Release
> > [2]
> https://dist.apache.org/repos/dist/dev/flink/flink-table-store-0.2.0-rc2/
> > [3]
> https://repository.apache.org/content/repositories/orgapacheflink-1523/
> > [4] https://dist.apache.org/repos/dist/release/flink/KEYS
> > [5]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12351570
> > [6] https://github.com/apache/flink-table-store/tree/release-0.2.0-rc2
> > [7] https://github.com/apache/flink-web/pull/562
> >
>

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

[Yu Li]

Congrats and welcome, Qingsheng and Shengkai!

Best Regards,
Yu


On Wed, 22 Jun 2022 at 17:43, Jiangang Liu 
wrote:

> Congratulations!
>
> Best,
> Jiangang Liu
>
> Mason Chen  于2022年6月22日周三 00:37写道：
>
> > Awesome work Qingsheng and Shengkai!
> >
> > Best,
> > Mason
> >
> > On Tue, Jun 21, 2022 at 4:53 AM Zhipeng Zhang 
> > wrote:
> >
> > > Congratulations, Qingsheng and ShengKai.
> > >
> > > Yang Wang  于2022年6月21日周二 19:43写道：
> > >
> > > > Congratulations, Qingsheng and ShengKai.
> > > >
> > > >
> > > > Best,
> > > > Yang
> > > >
> > > > Benchao Li  于2022年6月21日周二 19:33写道：
> > > >
> > > > > Congratulations!
> > > > >
> > > > > weijie guo  于2022年6月21日周二 13:44写道：
> > > > >
> > > > > > Congratulations, Qingsheng and ShengKai!
> > > > > >
> > > > > > Best regards,
> > > > > >
> > > > > > Weijie
> > > > > >
> > > > > >
> > > > > > Yuan Mei  于2022年6月21日周二 13:07写道：
> > > > > >
> > > > > > > Congrats Qingsheng and ShengKai!
> > > > > > >
> > > > > > > Best,
> > > > > > >
> > > > > > > Yuan
> > > > > > >
> > > > > > > On Tue, Jun 21, 2022 at 11:27 AM Terry Wang <
> zjuwa...@gmail.com>
> > > > > wrote:
> > > > > > >
> > > > > > > > Congratulations, Qingsheng and ShengKai!
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > Best,
> > > > > Benchao Li
> > > > >
> > > >
> > >
> > >
> > > --
> > > best,
> > > Zhipeng
> > >
> >
>

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

[Yu Li]

Congrats, Jingsong!

Best Regards,
Yu


On Wed, 15 Jun 2022 at 15:26, Sergey Nuyanzin  wrote:

> Congratulations, Jingsong!
>
> On Wed, Jun 15, 2022 at 8:45 AM Jingsong Li 
> wrote:
>
> > Thanks everyone.
> >
> > It's great to be with you in the Flink community!
> >
> > Best,
> > Jingsong
> >
> > On Wed, Jun 15, 2022 at 2:11 PM Yun Gao 
> > wrote:
> > >
> > > Congratulations, Jingsong!
> > >
> > > Best,
> > > Yun Gao
> > >
> > >
> > > --
> > > From:Jing Zhang 
> > > Send Time:2022 Jun. 14 (Tue.) 11:05
> > > To:dev 
> > > Subject:Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee
> > >
> > > Congratulations, Jingsong!
> > >
> > > Best,
> > > Jing Zhang
> > >
> > > Leonard Xu  于2022年6月14日周二 10:54写道：
> > >
> > > > Congratulations, Jingsong!
> > > >
> > > >
> > > > Best,
> > > > Leonard
> > > >
> > > > > 2022年6月13日 下午6:52，刘首维  写道：
> > > > >
> > > > > Congratulations and well deserved, Jingsong!
> > > > >
> > > > >
> > > > > Best regards,
> > > > > Shouwei
> > > > > --原始邮件--
> > > > > 发件人:
> > > > "dev"
> > > >   <
> > luoyu...@alumni.sjtu.edu.cn
> > > > ;
> > > > > 发送时间:2022年6月13日(星期一) 晚上6:09
> > > > > 收件人:"dev"mailto:dev@flink.apache.org
> > >;
> > > > >
> > > > > 主题:Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee
> > > > >
> > > > >
> > > > >
> > > > > Congratulations, Jingsong!
> > > > >
> > > > >
> > > > > Best regards,
> > > > > Yuxia
> > > > >
> > > > > - 原始邮件 -
> > > > > 发件人: "Yun Tang"  > > > > 收件人: "dev"  > > > > 发送时间: 星期一, 2022年 6 月 13日 下午 6:12:24
> > > > > 主题: Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee
> > > > >
> > > > > Congratulations, Jingsong! Well deserved.
> > > > >
> > > > > Best
> > > > > Yun Tang
> > > > > 
> > > > > From: Xingbo Huang  > > > > Sent: Monday, June 13, 2022 17:39
> > > > > To: dev  > > > > Subject: Re: [ANNOUNCE] New Apache Flink PMC Member - Jingsong Lee
> > > > >
> > > > > Congratulations, Jingsong!
> > > > >
> > > > > Best,
> > > > > Xingbo
> > > > >
> > > > > Jane Chan  > > > >
> > > > >  Congratulations, Jingsong!
> > > > > 
> > > > >  Best,
> > > > >  Jane Chan
> > > > > 
> > > > >  On Mon, Jun 13, 2022 at 4:43 PM Shuo Cheng <
> njucs...@gmail.com
> > > >  wrote:
> > > > > 
> > > > >   Congratulations, Jingsong!
> > > > >  
> > > > >   On 6/13/22, Paul Lam  > > > paullin3...@gmail.com> wrote:
> > > > >Congrats, Jingsong! Well deserved!
> > > > >   
> > > > >Best,
> > > > >Paul Lam
> > > > >   
> > > > >2022年6月13日 16:31，Lincoln Lee <
> > lincoln.8...@gmail.com
> > > >  写道：
> > > > >   
> > > > >Congratulations, Jingsong!
> > > > >   
> > > > >Best,
> > > > >Lincoln Lee
> > > > >   
> > > > >   
> > > > >Jark Wu  > imj...@gmail.com>
> > > > 于2022年6月13日周一 16:29写道：
> > > > >   
> > > > >Congrats, Jingsong!
> > > > >   
> > > > >Cheers,
> > > > >Jark
> > > > >   
> > > > >On Mon, 13 Jun 2022 at 16:16, Jiangang Liu <
> > > > >  liujiangangp...@gmail.com  > >
> > > > >wrote:
> > > > >   
> > > > >Congratulations, Jingsong!
> > > > >   
> > > > >Best,
> > > > >Jiangang Liu
> > > > >   
> > > > >Martijn Visser <
> martijnvis...@apache.org
> > > >  于2022年6月13日周一 16:06写道：
> > > > >   
> > > > >Like everyone has mentioned, this is
> > very
> > > > well deserved.
> > > > >Congratulations!
> > > > >   
> > > > >Op ma 13 jun. 2022 om 09:57 schreef
> > > > Benchao Li <
> > > > >  libenc...@apache.org 
> > > > >   :
> > > > >   
> > > > >Congratulations, Jingsong!
> > Well
> > > > deserved.
> > > > >   
> > > > >Rui Fan <1996fan...@gmail.com
> > > >  于2022年6月13日周一 15:53写道：
> > > > >   
> > > > >Congratulations, Jingsong!
> > > > >   
> > > > >Best,
> > > > >Rui Fan
> > > > >   
> > > > >On Mon, Jun 13, 2022 at 3:40
> > PM
> > > > LuNing Wang <
> > > > >  wang4lun...@gmail.com 
> > > > >   
> > > > >wrote:
> > > > >   
> > > > >Congratulations,
> Jingsong!
> > > > >   
> > > > >Best,
> > > > >LuNing Wang
> > > > >   
> > > > >Ingo Bürk <
> > > > airbla...@apache.org  于2022年6月13日周一
> > > > 15:36写道：
> > > > >   
> > > > >Congrats, Jingsong!
> > > > >   
> > > > >On 13.06.22 08:58,
> > Becket
> > > > Qin wrote:
> > > > >Hi all,
> > > > >   
> > > > >I'm very happy
> to
> > > > announce that Jingsong Lee has joined the
> > > > >Flink
> > > > >PMC!
> > > > >   
> > > > >Jingsong became
> a
> > > > Flink committer in Feb 2020 and has been
> > > > >continuously
> > > > >contributing to
> > the
> > > > 

[ANNOUNCE] Call for Presentations for ApacheCon Asia 2022 streaming track

[Yu Li]

Hi everyone,

ApacheCon Asia [1] will feature the Streaming track for the second year.
Please don't hesitate to submit your proposal if there is an interesting
project or Flink experience you would like to share with us!

The conference will be online (virtual) and the talks will be pre-recorded.
The deadline of proposal submission is at the end of this month (May 31st).

See you all there :)

Best Regards,
Yu

[1] https://apachecon.com/acasia2022/cfp.html

Re: [VOTE] Creating an Apache Flink slack workspace

[Yu Li]

+1 (binding)

Thanks Xintong for driving this!

Best Regards,
Yu


On Tue, 17 May 2022 at 16:32, Robert Metzger  wrote:

> Thanks for starting the VOTE!
>
> +1 (binding)
>
>
>
> On Tue, May 17, 2022 at 10:29 AM Jark Wu  wrote:
>
> > Thank Xintong for driving this work.
> >
> > +1 from my side (binding)
> >
> > Best,
> > Jark
> >
> > On Tue, 17 May 2022 at 16:24, Xintong Song 
> wrote:
> >
> > > Hi everyone,
> > >
> > > As previously discussed in [1], I would like to open a vote on creating
> > an
> > > Apache Flink slack workspace channel.
> > >
> > > The proposed actions include:
> > > - Creating a dedicated slack workspace with the name Apache Flink that
> is
> > > controlled and maintained by the Apache Flink PMC
> > > - Updating the Flink website about rules for using various
> communication
> > > channels
> > > - Setting up an Archive for the Apache Flink slack
> > > - Revisiting this initiative by the end of 2022
> > >
> > > The vote will last for at least 72 hours, and will be accepted by a
> > > consensus of active PMC members.
> > >
> > > Best,
> > >
> > > Xintong
> > >
> >
>

Re: [VOTE] Apache Flink Table Store 0.1.0, release candidate #2

[Yu Li]

+1 (binding)

- Checked release notes: *OK*
- Checked sums and signatures: *OK*
- Checked the jars in the staging repo: *OK*
- Checked source distribution doesn't include binaries: *OK*
- Maven clean install from source: *OK*
- Checked version consistency in pom files: *OK*
- Went through the quick start: *OK*
   - Minor: the set 'table-store.path' was not fully cleaned up after
dropping the table and exiting the sql client shell, please check whether
this is expected behavior.
- Checked the website updates: *OK*
  - Note: left some suggestions, please check.

Thanks for driving this release, Jingsong!

Best Regards,
Yu


On Sat, 7 May 2022 at 15:30, Becket Qin  wrote:

> Hi Jingsong,
>
> Thanks for driving the very first release of the flink-table-store!
>
> +1 (binding) for the RC.
>
> I verified the following:
> - the signature of the artifacts
> - the source jar does not contain binary files
> - no accidental distribution of other projects is included in the dist jar
> - went through the quick start
> - compiled the code locally
>
> There were two things that are not blockers but might worth noting:
> 1. Running the verification requires docker installation. It happens that I
> do not have that installed on my new laptop.
> 2. In the quick start, after dropping the word_count table, the Flink job
> that inserts data into the word_count table will keep failover. And this
> job won't exit after SQL Client exits. It is not a problem of
> flink-table-store, but it might be non-intuitive for some of the users.
>
> I also left some comment in the PR of release announcement.
>
> Thanks,
>
> Jiangjie (Becket) Qin
>
> On Thu, May 5, 2022 at 5:39 PM Jingsong Li  wrote:
>
> > Hi, Konstantin and OpenInx,
> >
> > I have updated https://github.com/apache/flink-web/pull/531 , you can
> > take a review~
> >
> > Best,
> > Jingsong
> >
> > On Thu, May 5, 2022 at 3:07 PM OpenInx  wrote:
> > >
> > > +1 ( non-binding) for the release. I agree with Konstantin that we can
> > add
> > > more materials about the table-store for the voting.
> > >
> > >
> > >1. Download the source tarball, signature (.asc), and checksum
> > >(.sha512):   OK
> > >2. Import gpg keys: download KEYS and run gpg --import
> > >/path/to/downloaded/KEYS (optional if this hasn’t changed) :  OK
> > >3. Verify the signature by running: gpg --verify
> > >flink-table-store-0.1.0-src.tgz.asc:  OK
> > >4. Verify the checksum by running: shasum -a 256 -c
> > >flink-table-store-0.1.0-src.tgz.sha512
> > flink-table-store-0.1.0-src.tgz :  OK
> > >5. Untar the archive and go into the source directory: tar xzf
> > >flink-table-store-0.1.0-src.tgz && cd flink-table-store-0.1.0:  OK
> > >6. Build and test the project: mvn clean package (use Java 8) :
>  All
> > >unit tests passed, except the e2e tests. Seems we will need to set
> up
> > a
> > >docker environment to run those e2e tests successfully.
> > >7. Verify the apache flink access table store:
> > >
> > > ./bin/sql-client.sh -j
> > >
> >
> /Users/openinx/Downloads/flink-table-store-0.1.0/flink-table-store-dist/target/flink-table-store-dist-0.1.0.jar
> > > embedded shell
> > >
> > > SET 'table-store.path' = '/Users/openinx/test/table-store' ;
> > >
> > > SET 'execution.runtime-mode'='batch';
> > >
> > > SET 'sql-client.execution.result-mode' = 'tableau';
> > >
> > > CREATE TABLE MyTable (
> > >
> > > user_id BIGINT,
> > >
> > > item_id BIGINT,
> > >
> > > behavior STRING,
> > >
> > > dt STRING,
> > >
> > > PRIMARY KEY (dt, user_id) NOT ENFORCED
> > >
> > > ) PARTITIONED BY (dt) WITH (
> > >
> > > 'bucket' = '4'
> > >
> > > );
> > >
> > > INSERT INTO MyTable VALUES
> > >
> > > (100, 200, 'buy', '2022-05-04'),
> > >
> > > (101, 201, 'save', '2022-05-04'),
> > >
> > > (101, 201, 'purchase', '2022-05-04');
> > >
> > >
> > > SELECT * FROM MyTable;
> > >
> > > +-+-+--++
> > >
> > > | user_id | item_id | behavior | dt |
> > >
> > > +-+-+--++
> > >
> > > | 100 | 200 | buy | 2022-05-04 |
> > >
> > > | 101 | 201 | purchase | 2022-05-04 |
> > >
> > > +-+-+--++
> > >
> > > 2 rows in set
> > >
> > > On Thu, May 5, 2022 at 2:39 PM Nicholas Jiang <
> nicholasji...@apache.org>
> > > wrote:
> > >
> > > > Hi everyone,
> > > >
> > > > +1 for the release (non-binding).
> > > >
> > > > - Built and compiled source codes [PASSED]
> > > > - Went through quick start guide [PASSED]
> > > > - Checked README.md [PASSED]
> > > > - Checked that use the table store jar to build query table
> application
> > > > [PASSED]
> > > >
> > > > Best regards,
> > > >
> > > > Nicholas Jiang
> > > >
> > > > On 2022/04/29 02:24:09 Jingsong Li wrote:
> > > > > Hi everyone,
> > > > >
> > > > > Please review and vote on the release candidate #2 for the version
> > 0.1.0
> > > > of
> > > > > Apache Flink Table Store, as follows:
> > > > >
> > > > > [ ] +1, Approve the release
> > > > > [ ] -1, Do 

Re: [ANNOUNCE] New Flink PMC member: Yang Wang

[Yu Li]

Congrats and welcome, Yang!

Best Regards,
Yu


On Fri, 6 May 2022 at 14:48, Paul Lam  wrote:

> Congrats, Yang! Well Deserved!
>
> Best,
> Paul Lam
>
> > 2022年5月6日 14:38，Yun Tang  写道：
> >
> > Congratulations, Yang!
> >
> > Best
> > Yun Tang
> > 
> > From: Jing Ge 
> > Sent: Friday, May 6, 2022 14:24
> > To: dev 
> > Subject: Re: [ANNOUNCE] New Flink PMC member: Yang Wang
> >
> > Congrats Yang and well Deserved!
> >
> > Best regards,
> > Jing
> >
> > On Fri, May 6, 2022 at 7:38 AM Lincoln Lee 
> wrote:
> >
> >> Congratulations Yang!
> >>
> >> Best,
> >> Lincoln Lee
> >>
> >>
> >> Őrhidi Mátyás  于2022年5月6日周五 12:46写道：
> >>
> >>> Congrats Yang! Well deserved!
> >>> Best,
> >>> Matyas
> >>>
> >>> On Fri, May 6, 2022 at 5:30 AM huweihua 
> wrote:
> >>>
>  Congratulations Yang!
> 
>  Best,
>  Weihua
> 
> 
> >>>
> >>
>
>

Re: [ANNOUNCE] Apache Flink 1.15.0 released

[Yu Li]

Hurray!

Thanks Yun Gao, Till and Joe for all the efforts as our release managers.
And thanks all contributors for making this happen!

Best Regards,
Yu


On Thu, 5 May 2022 at 18:01, Sergey Nuyanzin  wrote:

> Great news!
> Congratulations!
> Thanks to the release managers, and everyone involved.
>
> On Thu, May 5, 2022 at 11:57 AM godfrey he  wrote:
>
> > Congratulations~
> >
> > Thanks Yun, Till and Joe for driving this release
> > and everyone who made this release happen.
> >
> > Best,
> > Godfrey
> >
> > Becket Qin  于2022年5月5日周四 17:39写道：
> > >
> > > Hooray! Thanks Yun, Till and Joe for driving the release!
> > >
> > > Cheers,
> > >
> > > JIangjie (Becket) Qin
> > >
> > > On Thu, May 5, 2022 at 5:20 PM Timo Walther 
> wrote:
> > >
> > > > It took a bit longer than usual. But I'm sure the users will love
> this
> > > > release.
> > > >
> > > > Big thanks to the release managers!
> > > >
> > > > Timo
> > > >
> > > > Am 05.05.22 um 10:45 schrieb Yuan Mei:
> > > > > Great!
> > > > >
> > > > > Thanks, Yun Gao, Till, and Joe for driving the release, and thanks
> to
> > > > > everyone for making this release happen!
> > > > >
> > > > > Best
> > > > > Yuan
> > > > >
> > > > > On Thu, May 5, 2022 at 4:40 PM Leonard Xu 
> wrote:
> > > > >
> > > > >> Congratulations!
> > > > >>
> > > > >> Thanks Yun Gao, Till and Joe for the great work as our release
> > manager
> > > > and
> > > > >> everyone who involved.
> > > > >>
> > > > >> Best,
> > > > >> Leonard
> > > > >>
> > > > >>
> > > > >>
> > > > >>> 2022年5月5日 下午4:30，Yang Wang  写道：
> > > > >>>
> > > > >>> Congratulations!
> > > > >>>
> > > > >>> Thanks Yun Gao, Till and Joe for driving this release and
> everyone
> > who
> > > > >> made
> > > > >>> this release happen.
> > > > >>
> > > >
> > > >
> >
>
>
> --
> Best regards,
> Sergey
>

Re: FLINK-11746 work

[Yu Li]

Hi Chen,

Thanks for the interest to work on this.

Before assigning the JIRA and starting the upstream work, how about
reviving the discussion thread [1] first, making sure to reach a consensus
on the design and find committer resources for code review, according to
our code contribution process [2]?

Best Regards,
Yu

[1] https://lists.apache.org/thread/lp8xrzbhl70c2zbmd59zcbmtdhk1g8j2
[2]
https://flink.apache.org/contributing/contribute-code.html#code-contribution-process


On Tue, 12 Apr 2022 at 10:37, Chen Qin  wrote:

> Hi there,
>
> I would like to reboot discussion on FLINK-11746
>  work. Over the course
> of last two years, we managed to run a large number of critical flink apps
> (table/datastream) with underlying thrift format. It would be great if
> folks assign this jira to me so we would be able to kick off discussion on
> upstream work.
>
> Chen
>

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

[Yu Li]

Thanks for the efforts, Yun and Joe!

According to the earlier reply, the vote of RC1 is officially canceled,
right?

And just a reminder that there are still many open issues with FixVersion
marked as 1.15.0 [1] and I think most of them (if not all, meaning some
more bug fixes are still expected to be included in the next RC) could be
moved out, to clean up the release note and relative segment of the
blogpost.

Best Regards,
Yu

[1] https://s.apache.org/flink-1.15-open-issues


On Tue, 12 Apr 2022 at 19:03, Yun Gao  wrote:

> Hi Jing,
>
> No worry, very thanks for fixing the issue and informing us.
>
> I'll then head to create the rc2 today.
>
> Best,
> Yun
>
>
>  --Original Mail --
> Sender:Jing Zhang 
> Send Date:Tue Apr 12 18:55:30 2022
> Recipients:dev 
> Subject:Re: [VOTE] Release 1.15.0, release candidate #1
> Hi, Yun Gao
> There is a new bug [1] introduced in release-1.15.
> It's better to be fixed in 1.15.0 version.
> I'm terribly sorry to merge the pull request too late.
>
> [1] https://issues.apache.org/jira/browse/FLINK-26681
>
> Best,
> Jing Zhang
>
> Johannes Moser  于2022年4月12日周二 14:53写道：
>
> > Here is the missing link to the announcement blogpost [6]
> >
> > [6] https://github.com/apache/flink-web/pull/526
> >
> > > On 11.04.2022, at 20:12, Yun Gao  wrote:
> > >
> > > Hi everyone,
> > >
> > > Please review and vote on the release candidate #1 for the version
> > 1.15.0, as follows:
> > > [ ] +1, Approve the release
> > > [ ] -1, Do not approve the release (please provide specific comments)
> > > The complete staging area is available for your review, which includes:
> > > * JIRA release notes [1],
> > > * the official Apache source release and binary convenience releases to
> > be deployed to dist.apache.org [2], which are signed with the key with
> > fingerprint CBE82BEFD827B08AFA843977EDBF922A7BC84897 [3],
> > > * all artifacts to be deployed to the Maven Central Repository [4],
> > > * source code tag "release-1.15.0-rc1" [5],
> > > * website pull request listing the new release and adding announcement
> > blog post [6].
> > > The vote will be open for at least 72 hours. It is adopted by majority
> > approval, with at least 3 PMC affirmative votes.
> > > Thanks,
> > > Joe, Till and Yun Gao
> > > [1]
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12350442
> > > [2] https://dist.apache.org/repos/dist/dev/flink/flink-1.15.0-rc1/
> > > [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> > > [4]
> > https://repository.apache.org/content/repositories/orgapacheflink-1494/
> > > [5] https://github.com/apache/flink/releases/tag/release-1.15.0-rc1[6]
> > https://github.com/apache/flink-web/pull/526
> >
> >
>

Re: Contributing to FLINK-27195

[Yu Li]

Hi Mason,

Thanks for the efforts. I could see that Ingo has already assigned it to
you (and thanks Ingo for the action).

Best Regards,
Yu


On Tue, 12 Apr 2022 at 14:42, Mason Chen  wrote:

> Hi Devs,
>
> Could a committer assign me this ticket:
> https://issues.apache.org/jira/browse/FLINK-27195? I have been taking a
> deeper look into the Kafka Source and would like to contribute back a
> bugfix. I have a minimal test case and the fix should be simple. Thanks
> all!
>
> Best,
> Mason
>

Re: Re: Weekly 1.15 Sync tomorrow cancelled

[Yu Li]

Thanks for the update Yun, and thanks all for the efforts! Look forward to
the first RC.

Best Regards,
Yu


On Tue, 22 Mar 2022 at 15:28, Yun Gao  wrote:

> Hi Yu,
>
> Currently we still have some ongoing blocker issues tracked under [1].
>
> We are tighly tracking the progress of these issues and we'll start
> creating
> the RC0 immediately after these blockers are solved, and hopefully inside
> this week.
>
> Best,
> Yun Gao
>
>
> [1]
> https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=505=detail=FLINK-26779
>
>
>
> ------Original Mail --
> *Sender:*Yu Li 
> *Send Date:*Tue Mar 22 15:25:17 2022
> *Recipients:*dev 
> *Subject:*Re: Weekly 1.15 Sync tomorrow cancelled
>
>> Thanks for the note Joe. Could you share with us the status of RC0
>> preparation and when it's planned to be created? Many thanks.
>>
>> Best Regards,
>> Yu
>>
>>
>> On Tue, 22 Mar 2022 at 04:00, Johannes Moser  wrote:
>>
>> > Hello,
>> >
>>
>> > As all relevant issues are assigned and worked on there’s no need to sync
>> > tomorrow.
>> >
>> > Therefor we decided to cancel the sync.
>> >
>> > Best,
>> > Joe
>>
>

Re: Weekly 1.15 Sync tomorrow cancelled

[Yu Li]

Thanks for the note Joe. Could you share with us the status of RC0
preparation and when it's planned to be created? Many thanks.

Best Regards,
Yu


On Tue, 22 Mar 2022 at 04:00, Johannes Moser  wrote:

> Hello,
>
> As all relevant issues are assigned and worked on there’s no need to sync
> tomorrow.
>
> Therefor we decided to cancel the sync.
>
> Best,
> Joe

[ANNOUNCE] New PMC member: Yuan Mei

[Yu Li]

Hi all!

I'm very happy to announce that Yuan Mei has joined the Flink PMC!

Yuan is helping the community a lot with creating and validating releases,
contributing to FLIP discussions and good code contributions to the
state backend and related components.

Congratulations and welcome, Yuan!

Best Regards,
Yu (On behalf of the Apache Flink PMC)

Re: [ANNOUNCE] New Apache Flink Committer - David Morávek

[Yu Li]

Congrats, David!

Best Regards,
Yu


On Tue, 8 Mar 2022 at 16:11, Johannes Moser  wrote:

> Very well deserved.
>
> > On 08.03.2022, at 05:43, Lincoln Lee  wrote:
> >
> > Congratulations David!
> >
> > Best,
> > Lincoln Lee
> >
> >
> > Yun Gao  于2022年3月8日周二 11:24写道：
> >
> >> Congratulations David!
> >>
> >> Best,
> >> Yun Gao
> >>
> >>
> >> --
> >> From:Jing Zhang 
> >> Send Time:2022 Mar. 8 (Tue.) 11:10
> >> To:dev 
> >> Subject:Re: [ANNOUNCE] New Apache Flink Committer - David Morávek
> >>
> >> Congratulations David!
> >>
> >> Ryan Skraba  于2022年3月7日周一 22:18写道：
> >>
> >>> Congratulations David!
> >>>
> >>> On Mon, Mar 7, 2022 at 9:54 AM Jan Lukavský  wrote:
> >>>
>  Congratulations David!
> 
>   Jan
> 
>  On 3/7/22 09:44, Etienne Chauchot wrote:
> > Congrats David !
> >
> > Well deserved !
> >
> > Etienne
> >
> > Le 07/03/2022 à 08:47, David Morávek a écrit :
> >> Thanks everyone!
> >>
> >> Best,
> >> D.
> >>
> >> On Sun 6. 3. 2022 at 9:07, Yuan Mei  wrote:
> >>
> >>> Congratulations, David!
> >>>
> >>> Best Regards,
> >>> Yuan
> >>>
> >>> On Sat, Mar 5, 2022 at 8:13 PM Roman Khachatryan  >>>
> >>> wrote:
> >>>
>  Congratulations, David!
> 
>  Regards,
>  Roman
> 
>  On Fri, Mar 4, 2022 at 7:54 PM Austin Cawley-Edwards
>   wrote:
> > Congrats David!
> >
> > On Fri, Mar 4, 2022 at 12:18 PM Zhilong Hong <
> >> zhlongh...@gmail.com
> 
>  wrote:
> >> Congratulations, David!
> >>
> >> Best,
> >> Zhilong
> >>
> >> On Sat, Mar 5, 2022 at 1:09 AM Piotr Nowojski <
> >>> pnowoj...@apache.org
> >
> >> wrote:
> >>
> >>> Congratulations :)
> >>>
> >>> pt., 4 mar 2022 o 16:04 Aitozi 
> >>> napisał(a):
> >>>
>  Congratulations David!
> 
>  Ingo Bürk  于2022年3月4日周五 22:56写道：
> 
> > Congrats, David!
> >
> > On 04.03.22 12:34, Robert Metzger wrote:
> >> Hi everyone,
> >>
> >> On behalf of the PMC, I'm very happy to announce David
> >>> Morávek
>  as a
> >>> new
> >> Flink committer.
> >>
> >> His first contributions to Flink date back to 2019. He has
> >>> been
> >> increasingly active with reviews and driving major
> >>> initiatives
>  in
> >> the
> >> community. David brings valuable experience from being a
>  committer
> >> in
>  the
> >> Apache Beam project to Flink.
> >>
> >>
> >> Please join me in congratulating David for becoming a Flink
> >>> committer!
> >> Cheers,
> >> Robert
> >>
> 
> >>>
> >>
>
>

Re: [ANNOUNCE] New Apache Flink Committer - Martijn Visser

[Yu Li]

Congratulations!

Best Regards,
Yu


On Fri, 4 Mar 2022 at 10:31, Zhipeng Zhang  wrote:

> Congratulations Martijn!
>
> Qingsheng Ren  于2022年3月4日周五 10:14写道：
>
> > Congratulations Martijn!
> >
> > Best regards,
> >
> > Qingsheng Ren
> >
> > > On Mar 4, 2022, at 9:56 AM, Leonard Xu  wrote:
> > >
> > > Congratulations and well deserved Martjin !
> > >
> > > Best,
> > > Leonard
> > >
> > >> 2022年3月4日 上午7:55，Austin Cawley-Edwards  写道：
> > >>
> > >> Congrats Martijn!
> > >>
> > >> On Thu, Mar 3, 2022 at 10:50 AM Robert Metzger 
> > wrote:
> > >>
> > >>> Hi everyone,
> > >>>
> > >>> On behalf of the PMC, I'm very happy to announce Martijn Visser as a
> > new
> > >>> Flink committer.
> > >>>
> > >>> Martijn is a very active Flink community member, driving a lot of
> > efforts
> > >>> on the dev@flink mailing list. He also pushes projects such as
> > replacing
> > >>> Google Analytics with Matomo, so that we can generate our web
> analytics
> > >>> within the Apache Software Foundation.
> > >>>
> > >>> Please join me in congratulating Martijn for becoming a Flink
> > committer!
> > >>>
> > >>> Cheers,
> > >>> Robert
> > >>>
> > >
> >
> >
>
> --
> best,
> Zhipeng
>

Re: Change of focus

[Yu Li]

Thanks for everything, Till! You are such a great mentor and workmate, and
we will definitely miss you...

Wish you all the best for the new adventure, and be sure to let me know
when you plan to visit Beijing someday in the future!

Best Regards,
Yu


On Wed, 2 Mar 2022 at 16:09, Jingsong Li  wrote:

> Hi Till,
>
> Good luck with the next chapter, and thanks for all of your efforts.
>
> Best,
> Jingsong
>
> On Wed, Mar 2, 2022 at 2:57 PM Yufei Zhang  wrote:
> >
> > Hi Till,
> >
> > Thank you Till, and good luck in your next chapter :)
> >
> > Cheers,
> > Yufei
> >
> > On Mon, Feb 28, 2022 at 6:59 PM Till Rohrmann 
> wrote:
> >
> > > Hi everyone,
> > >
> > > I wanted to let you know that I will be less active in the community
> > > because I’ve decided to start a new chapter in my life. Hence, please
> don’t
> > > wonder if I might no longer be very responsive on mails and JIRA
> issues.
> > >
> > > It is great being part of such a great community with so many amazing
> > > people. Over the past 7,5 years, I’ve learned a lot thanks to you and
> > > together we have shaped how people think about stream processing
> nowadays.
> > > This is something we can be very proud of. I am sure that the community
> > > will continue innovating and setting the pace for what is possible with
> > > real time processing. I wish you all godspeed!
> > >
> > > Cheers,
> > > Till
> > >
>

Re: [ANNOUNCE] New Flink PMC members: Igal Shilman, Konstantin Knauf and Yun Gao

[Yu Li]

Congratulations!

Best Regards,
Yu


On Fri, 18 Feb 2022 at 14:19, godfrey he  wrote:

> Congratulations!
>
> Best,
> Godfrey
>
> Lincoln Lee  于2022年2月18日周五 14:07写道：
> >
> > Congratulations!
> >
> > Best,
> > Lincoln Lee
> >
> >
> > Jingsong Li  于2022年2月18日周五 12:42写道：
> >
> > > Congratulations!
> > >
> > > Best,
> > > Jingsong
> > >
> > > On Thu, Feb 17, 2022 at 8:08 PM Jinzhong Li 
> > > wrote:
> > > >
> > > > Congratulations!
> > > >
> > > >
> > > > Best,
> > > >
> > > > Jinzhong
> > > >
> > > > On Wed, Feb 16, 2022 at 9:23 PM Robert Metzger 
> > > wrote:
> > > >
> > > > > Hi all,
> > > > >
> > > > > I would like to formally announce a few new Flink PMC members on
> the
> > > dev@
> > > > > list. The PMC has not done a good job of always announcing new PMC
> > > members
> > > > > (and committers) recently. I'll try to keep an eye on this in the
> > > future to
> > > > > improve the situation.
> > > > >
> > > > > Nevertheless, I'm very happy to announce some very active community
> > > members
> > > > > as new PMC members:
> > > > >
> > > > > - Igal Shilman, added to the PMC in October 2021
> > > > > - Konstantin Knauf, added to the PMC in January 2022
> > > > > - Yun Gao, added to the PMC in February 2022
> > > > >
> > > > > Please join me in welcoming them to the Flink PMC!
> > > > >
> > > > > Best,
> > > > > Robert
> > > > >
> > >
>

Re: Re: [ANNOUNCE] New Apache Flink Committers: Feng Wang, Zhipeng Zhang

[Yu Li]

Congratulations!

Best Regards,
Yu


On Fri, 18 Feb 2022 at 14:19, godfrey he  wrote:

> Congratulations!
>
> Best,
> Godfrey
>
> Lincoln Lee  于2022年2月18日周五 14:05写道：
> >
> > Congratulations Feng and Zhipeng!
> >
> > Best,
> > Lincoln Lee
> >
> >
> > Yuepeng Pan  于2022年2月18日周五 12:45写道：
> >
> > >
> > >
> > >
> > > Congratulations!
> > >
> > >
> > > Best,
> > > Yuepeng Pan
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > 在 2022-02-18 12:41:18，"Jingsong Li"  写道：
> > > >Congratulations!
> > > >
> > > >Best,
> > > >Jingsong
> > > >
> > > >On Fri, Feb 18, 2022 at 9:47 AM Zhipeng Zhang <
> zhangzhipe...@gmail.com>
> > > wrote:
> > > >>
> > > >> Thank you everyone for the warm welcome!
> > > >>
> > > >> Best,
> > > >> Zhipeng
> > > >>
> > > >> Jinzhong Li  于2022年2月17日周四 19:58写道：
> > > >>
> > > >> > Congratulations!
> > > >> >
> > > >> >
> > > >> > Best,
> > > >> >
> > > >> > Jinzhong
> > > >> >
> > > >> > Robert Metzger  于2022年2月16日周三 21:32写道：
> > > >> >
> > > >> > > Hi everyone,
> > > >> > >
> > > >> > > On behalf of the PMC, I'm very happy to announce two new Flink
> > > >> > > committers: Feng Wang and Zhipeng Zhang!
> > > >> > >
> > > >> > > Feng is one of the most active Flink evangelists in China, with
> > > plenty of
> > > >> > > public talks, blog posts and other evangelization activities.
> The
> > > PMC
> > > >> > wants
> > > >> > > to recognize and value these efforts by making Feng a committer!
> > > >> > >
> > > >> > > Zhipeng Zhang has made significant contributions to flink-ml,
> like
> > > most
> > > >> > of
> > > >> > > the FLIPs for our ML efforts.
> > > >> > >
> > > >> > > Please join me in welcoming them as committers!
> > > >> > >
> > > >> > >
> > > >> > > Best,
> > > >> > > Robert
> > > >> > >
> > > >> >
> > > >>
> > > >>
> > > >> --
> > > >> best,
> > > >> Zhipeng
> > >
>

Re: [VOTE] FLIP-203: Incremental savepoints

[Yu Li]

+1 (binding)

Thanks for driving this Piotr! Just one more (belated) suggestion: in the
"Checkpoint vs savepoint guarantees" section, there are still question
marks scattered in the table, and I suggest putting all TODO works into the
"Limitations" section, or adding a "Future Work" section, for easier later
tracking.

Best Regards,
Yu


On Mon, 24 Jan 2022 at 18:48, Konstantin Knauf  wrote:

> Thanks, Piotr. Proposal looks good.
>
> +1 (binding)
>
> On Mon, Jan 24, 2022 at 11:20 AM David Morávek  wrote:
>
> > +1 (non-binding)
> >
> > Best,
> > D.
> >
> > On Mon, Jan 24, 2022 at 10:54 AM Dawid Wysakowicz <
> dwysakow...@apache.org>
> > wrote:
> >
> > > +1 (binding)
> > >
> > > Best,
> > >
> > > Dawid
> > >
> > > On 24/01/2022 09:56, Piotr Nowojski wrote:
> > > > Hi,
> > > >
> > > > As there seems to be no further questions about the FLIP-203 [1] I
> > would
> > > > propose to start a voting thread for it.
> > > >
> > > > For me there are still two unanswered questions, whether we want to
> > > support
> > > > schema evolution and State Processor API with native format snapshots
> > or
> > > > not. But I would propose to tackle them as follow ups, since those
> are
> > > > pre-existing issues of the native format checkpoints, and could be
> done
> > > > completely independently of providing the native format support in
> > > > savepoints.
> > > >
> > > > Best,
> > > > Piotrek
> > > >
> > > > [1]
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-203%3A+Incremental+savepoints
> > > >
> > >
> >
>
>
> --
>
> Konstantin Knauf
>
> https://twitter.com/snntrable
>
> https://github.com/knaufk
>

Re: [DISCUSS] Pushing Apache Flink 1.15 Feature Freeze

[Yu Li]

+1 to extend the feature freeze date to Feb. 14th, which might be a good
Valentine's Day present for all Flink developers as well (smile).

Best Regards,
Yu


On Wed, 26 Jan 2022 at 14:50, Yuan Mei  wrote:

> +1 extending feature freeze for one week.
>
> Code Freeze on 6th (end of Spring Festival) is equivalent to say code
> freeze at the end of this week for Chinese buddies, since Spring Festival
> starts next week.
> It also means they should be partially available during the holiday,
> otherwise they would block the release if any unexpected issues arise.
>
> The situation sounds a bit stressed and can be resolved very well by
> extending the freeze date for a bit.
>
> Best
> Yuan
>
> On Wed, Jan 26, 2022 at 11:18 AM Yun Tang  wrote:
>
> > Since the official Spring Festival holidays in China starts from Jan 31th
> > to Feb 6th, and many developers in China would enjoy the holidays at that
> > time.
> > +1 for extending the feature freeze.
> >
> > Best
> > Yun Tang
> > 
> > From: Jingsong Li 
> > Sent: Wednesday, January 26, 2022 10:32
> > To: dev 
> > Subject: Re: [DISCUSS] Pushing Apache Flink 1.15 Feature Freeze
> >
> > +1 for extending the feature freeze.
> >
> > Thanks Joe for driving.
> >
> > Best,
> > Jingsong
> >
> > On Wed, Jan 26, 2022 at 12:04 AM Martijn Visser 
> > wrote:
> > >
> > > Hi all,
> > >
> > > +1 for extending the feature freeze. We could use the time to try to
> wrap
> > > up some important SQL related features and improvements.
> > >
> > > Best regards,
> > >
> > > Martijn
> > >
> > > On Tue, 25 Jan 2022 at 16:38, Johannes Moser 
> wrote:
> > >
> > > > Dear Flink community,
> > > >
> > > > as mentioned in the summary mail earlier some contributors voiced
> that
> > > > they would benefit from pushing the feature freeze for 1.15. by a
> week.
> > > > This would mean Monday, 14th of February 2022, end of business CEST.
> > > >
> > > > Please let us know in case you got any concerns.
> > > >
> > > >
> > > > Best,
> > > > Till, Yun Gao & Joe
> >
>

Re: [DISCUSS] FLIP-203: Incremental savepoints

[Yu Li]

Thanks for the update, Piotr!

> Is `state.backend.incremental` the only configuration parameter that can
be
> used in this context?
According to FLIP-193 [1], all the existing checkpoint configurations are
actually for *Snapshot*, ownership (lifecycle) is the only difference
between Checkpoints and Savepoints, and I suggest we keep the description
aligned with FLIP-193.

> a) What about RocksDB upgrades? If we bump RocksDB version between Flink
> versions, do we support recovering from a native format snapshot
> (incremental checkpoint)?
Below are my two cents:
* The functionality of incremental native-format savepoint is (like
*snapshot* in traditional database [2]) to (fast) produce a persisted,
self-contained version of the current state of the job for point-in-time
recovery, but cannot replace canonical savepoint (like *backup* in
traditional database) for upgrading or state-backend-switching, etc.
* We prefer such functionality to be supplied by a *savepoint* instead of a
(retained) *checkpoint* because the life-cycle of the data should be
user-controlled rather than system-controlled [1].
* If we'd like to cover all functionalities the canonical savepoint has
now, the design for incremental *canonical-format* savepoint would be
required, which is more complicated and could be considered as future work.

Best Regards,
Yu

[1]
https://cwiki.apache.org/confluence/display/FLINK/FLIP-193%3A+Snapshots+ownership
[2] https://www.hitechnectar.com/blogs/snapshot-vs-backup/


On Thu, 13 Jan 2022 at 19:40, Piotr Nowojski  wrote:

> Hi,
>
> Thanks for the comments and questions. Starting from the top:
>
> Seth: good point about schema evolution. Actually, I have a very similar
> question to State Processor API. Is it the same scenario in this case?
> Should it also be working with checkpoints but might be just untested?
>
> And next question, should we commit to supporting those two things (State
> Processor API and schema evolution) for native savepoints? What about
> aligned checkpoints? (please check [1] for that).
>
> Yu Li: 1, 2 and 4 done.
>
> > 3. How about changing the description of "the default configuration of
> the
> > checkpoints will be used to determine whether the savepoint should be
> > incremental or not" to something like "the `state.backend.incremental`
> > setting now denotes the type of native format snapshot and will take
> effect
> > for both checkpoint and savepoint (with native type)", to prevent concept
> > confusion between checkpoint and savepoint?
>
> Is `state.backend.incremental` the only configuration parameter that can be
> used in this context? I would guess not? What about for example
> "state.storage.fs.memory-threshold" or all of the Advanced RocksDB State
> Backends Options [2]?
>
> David:
>
> > does this mean that we need to keep the checkpoints compatible across
> minor
> > versions? Or can we say, that the minor version upgrades are only
> > guaranteed with canonical savepoints?
>
> Good question. Frankly I was always assuming that this is implicitly given.
> Otherwise users would not be able to recover jobs that are failing because
> of bugs in Flink. But I'm pretty sure that was never explicitly stated.
>
> As Konstantin suggested, I've written down the pre-existing guarantees of
> checkpoints and savepoints followed by two proposals on how they should be
> changed [1]. Could you take a look?
>
> I'm especially unsure about the following things:
> a) What about RocksDB upgrades? If we bump RocksDB version between Flink
> versions, do we support recovering from a native format snapshot
> (incremental checkpoint)?
> b) State Processor API - both pre-existing and what do we want to provide
> in the future
> c) Schema Evolution - both pre-existing and what do we want to provide in
> the future
>
> Best,
> Piotrek
>
> [1]
>
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-203%3A+Incremental+savepoints#FLIP203:Incrementalsavepoints-Checkpointvssavepointguarantees
> [2]
>
> https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/config/#advanced-rocksdb-state-backends-options
>
> wt., 11 sty 2022 o 09:45 Konstantin Knauf  napisał(a):
>
> > Hi Piotr,
> >
> > would it be possible to provide a table that shows the
> > compatibility guarantees provided by the different snapshots going
> forward?
> > Like type of change (Topology. State Schema, Parallelism, ..) in one
> > dimension, and type of snapshot as the other dimension. Based on that, it
> > would be easier to discuss those guarantees, I believe.
> >
> > Cheers,
> >
> > Konstantin
> >
> > On Mon, Jan 3, 2022 at 9:11 AM David Morávek  wrote:
> >
> > &

Re: [VOTE] Create a separate sub project for FLIP-188: flink-store

[Yu Li]

+1 for a separate repository and release pipeline in the same way as
flink-statefun [1], flink-ml [2] and the coming flink-connectors [3].

+1 for naming it as "flink-table-store" (I'm also ok with
"flink-table-storage", but slightly prefer "flink-table-store" because it's
shorter)

Thanks for driving this Jingsong, and look forward to a fast evolution of
this direction!

Best Regards,
Yu

[1] https://github.com/apache/flink-statefun
[2] https://github.com/apache/flink-ml
[3] https://github.com/apache/flink-connectors


On Mon, 10 Jan 2022 at 10:52, Jingsong Li  wrote:

> Hi David, thanks for your suggestion.
>
> I think we should re-use as many common components with connectors as
> possible. I don't fully understand what you mean, but for this project
> I prefer to use Maven rather than Gradle.
>
> Best,
> Jingsong
>
> On Fri, Jan 7, 2022 at 11:59 PM David Morávek  wrote:
> >
> > +1 for the separate repository under the Flink umbrella
> >
> > as we've already started creating more repositories with connectors,
> would
> > it be possible to re-use the same build infrastructure for this one? (eg.
> > shared set of Gradle plugins that unify the build experience)?
> >
> > Best,
> > D.
> >
> > On Fri, Jan 7, 2022 at 11:31 AM Jingsong Li 
> wrote:
> >
> > > For more references on `store` and `storage`:
> > >
> > > For example,
> > >
> > > Rocksdb is a library that provides an embeddable, persistent key-value
> > > store for fast storage. [1]
> > >
> > > Apache HBase [1] is an open-source, distributed, versioned,
> > > column-oriented store modeled after Google' Bigtable. [2]
> > >
> > > [1] https://github.com/facebook/rocksdb
> > > [2] https://github.com/apache/hbase
> > >
> > > Best,
> > > Jingsong
> > >
> > > On Fri, Jan 7, 2022 at 6:17 PM Jingsong Li 
> wrote:
> > > >
> > > > Thanks all,
> > > >
> > > > Combining everyone's comments, I recommend using `flink-table-store`:
> > > >
> > > > ## table
> > > > something to do with table storage (From Till). Not only flink-table,
> > > > but also for user-oriented tables.
> > > >
> > > > ## store vs storage
> > > > - The first point I think, store is better pronounced, storage is
> > > > three syllables while store is two syllables
> > > > - Yes, store also stands for shopping. But I think the English
> > > > polysemy is also quite interesting, a store to store various items,
> it
> > > > also feels interesting to represent the feeling that we want to do
> > > > data storage.
> > > > - The first feeling is, storage is a physical object or abstract
> > > > concept, store is a software application or entity
> > > >
> > > > So I prefer `flink-table-store`, what do you think?
> > > >
> > > > (@_@ Naming is too difficult)
> > > >
> > > > Best,
> > > > Jingsong
> > > >
> > > > On Fri, Jan 7, 2022 at 5:37 PM Konstantin Knauf 
> > > wrote:
> > > > >
> > > > > +1 to a separate repository assuming this repository will still be
> > > part of
> > > > > Apache Flink (same PMC, Committers). I am not aware we have
> something
> > > like
> > > > > "sub-projects" officially.
> > > > >
> > > > > I share Till and Timo's concerns regarding "store".
> > > > >
> > > > > On Fri, Jan 7, 2022 at 9:59 AM Till Rohrmann  >
> > > wrote:
> > > > >
> > > > > > +1 for the separate project.
> > > > > >
> > > > > > I would agree that flink-store is not the best name.
> flink-storage >
> > > > > > flink-store but I would even more prefer a name that conveys
> that it
> > > has
> > > > > > something to do with table storage.
> > > > > >
> > > > > > Cheers,
> > > > > > Till
> > > > > >
> > > > > > On Fri, Jan 7, 2022 at 9:14 AM Timo Walther 
> > > wrote:
> > > > > >
> > > > > > > +1 for the separate project
> > > > > > >
> > > > > > > But maybe use `flink-storage` instead of `flink-store`?
> > > > > > >
> > > > > > > I'm not a native speaker but store is defined as "A place where
> > > items
> > > > > > > may be purchased.". It almost sounds like the `flink-packages`
> > > project.
> > > > > > >
> > > > > > > Regards,
> > > > > > > Timo
> > > > > > >
> > > > > > >
> > > > > > > On 07.01.22 08:37, Jingsong Li wrote:
> > > > > > > > Hi everyone,
> > > > > > > >
> > > > > > > > I'd like to start a vote for create a separate sub project
> for
> > > > > > > > FLIP-188 [1]: `flink-store`.
> > > > > > > >
> > > > > > > > - If you agree with the name `flink-store`, please just +1
> > > > > > > > - If you have a better suggestion, please write your
> suggestion,
> > > > > > > > followed by a reply that can +1 to the name that has appeared
> > > > > > > > - If you do not want it to be a subproject of flink, just -1
> > > > > > > >
> > > > > > > > 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/display/FLINK/FLIP-188%3A+Introduce+Built-in+Dynamic+Table+Storage
> > > > > > > >
> > > > > > > > Best,
> > > > > > > > Jingsong
> > > > > > > >
> > > 

Re: [DISCUSS] FLIP-203: Incremental savepoints

[Yu Li]

Thanks for the proposal Piotr! Overall I'm +1 for the idea, and below are
my two cents:

1. How about adding a "Term Definition" section and clarify what "native
format" (the "native" data persistence format of the current state backend)
and "canonical format" (the "uniform" format that supports switching state
backends) means?

2. IIUC, currently the FLIP proposes to only support incremental savepoint
with native format, and there's no plan to add such support for canonical
format, right? If so, how about writing this down explicitly in the FLIP
doc, maybe in a "Limitations" section, plus the fact that
`HashMapStateBackend` cannot support incremental savepoint before FLIP-151
is done? (side note: @Roman just a kindly reminder, that please take
FLIP-203 into account when implementing FLIP-151)

3. How about changing the description of "the default configuration of the
checkpoints will be used to determine whether the savepoint should be
incremental or not" to something like "the `state.backend.incremental`
setting now denotes the type of native format snapshot and will take effect
for both checkpoint and savepoint (with native type)", to prevent concept
confusion between checkpoint and savepoint?

4. How about putting the notes of behavior change (the default type of
savepoint will be changed to `native` in the future, and by then the taken
savepoint cannot be used to switch state backends by default) to a more
obvious place, for example moving from the "CLI" section to the
"Compatibility" section? (although it will only happen in 1.16 release
based on the proposed plan)

And all above suggestions apply for our user-facing document after the FLIP
is (partially or completely, accordingly) done, if taken (smile).

Best Regards,
Yu


On Tue, 21 Dec 2021 at 22:23, Seth Wiesman  wrote:

> >> AFAIK state schema evolution should work both for native and canonical
> >> savepoints.
>
> Schema evolution does technically work for both formats, it happens after
> the code paths have been unified, but the community has up until this point
> considered that an unsupported feature. From my perspective making this
> supported could be as simple as adding test coverage but that's an active
> decision we'd need to make.
>
> On Tue, Dec 21, 2021 at 7:43 AM Piotr Nowojski 
> wrote:
>
> > Hi Konstantin,
> >
> > > In this context: will the native format support state schema evolution?
> > If
> > > not, I am not sure, we can let the format default to native.
> >
> > AFAIK state schema evolution should work both for native and canonical
> > savepoints.
> >
> > Regarding what is/will be supported we will document as part of this
> > FLIP-203. But it's not as simple as just the difference between native
> and
> > canonical formats.
> >
> > Best, Piotrek
> >
> > pon., 20 gru 2021 o 14:28 Konstantin Knauf 
> napisał(a):
> >
> > > Hi Piotr,
> > >
> > > Thanks a lot for starting the discussion. Big +1.
> > >
> > > In my understanding, this FLIP introduces the snapshot format as a
> > *really*
> > > user facing concept. IMO it is important that we document
> > >
> > > a) that it is not longer the checkpoint/savepoint characteristics that
> > > determines the kind of changes that a snapshots allows (user code,
> state
> > > schema evolution, topology changes), but now this becomes a property of
> > the
> > > format regardless of whether this is a snapshots or a checkpoint
> > > b) the exact changes that each format allows (code, state schema,
> > topology,
> > > state backend, max parallelism)
> > >
> > > In this context: will the native format support state schema evolution?
> > If
> > > not, I am not sure, we can let the format default to native.
> > >
> > > Thanks,
> > >
> > > Konstantin
> > >
> > >
> > > On Mon, Dec 20, 2021 at 2:09 PM Piotr Nowojski 
> > > wrote:
> > >
> > > > Hi devs,
> > > >
> > > > I would like to start a discussion about a previously announced
> follow
> > up
> > > > of the FLIP-193 [1], namely allowing savepoints to be in native
> format
> > > and
> > > > incremental. The changes do not seem invasive. The full proposal is
> > > > written down as FLIP-203: Incremental savepoints [2]. Please take a
> > look,
> > > > and let me know what you think.
> > > >
> > > > Best,
> > > > Piotrek
> > > >
> > > > [1]
> > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-193%3A+Snapshots+ownership
> > > > [2]
> > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-203%3A+Incremental+savepoints#FLIP203:Incrementalsavepoints-Semantic
> > > >
> > >
> > >
> > > --
> > >
> > > Konstantin Knauf
> > >
> > > https://twitter.com/snntrable
> > >
> > > https://github.com/knaufk
> > >
> >
>

Re: [VOTE] Release 1.11.6/1.12.7/1.13.5/1.14.2, release candidate #1

[Yu Li]

+1

* Verified checksums and signatures
* Reviewed website PR
   - Minor: left a comment to mention CVE-2021-45046
* Checked and confirmed new tags only contain log4j version bump
* Checked release notes and found no issues
   - I've moved FLINK-25317 to 1.14.3

Thanks for driving these releases Chesnay!

Best Regards,
Yu


On Wed, 15 Dec 2021 at 21:29, Chesnay Schepler  wrote:

> FYI; the publication of the python release for 1.11/1.12 will be delayed
> because we hit the project size limit on pypi again, and increasing that
> limit may take a while.
> On the positive side, this gives us more time to fix the mac builds.
>
> On 15/12/2021 03:55, Chesnay Schepler wrote:
> > Hi everyone,
> >
> > This vote is for the emergency patch releases for 1.11, 1.12, 1.13 and
> > 1.14 to address CVE-2021-44228/CVE-2021-45046.
> > It covers all 4 releases as they contain the same changes (upgrading
> > Log4j to 2.16.0) and were prepared simultaneously by the same person.
> > (Hence, if something is broken, it likely applies to all releases)
> >
> > Note: 1.11/1.12 are still missing the Python Mac releases.
> >
> >
> > Please review and vote on the release candidate #1 for the versions
> > 1.11.6, 1.12.7, 1.13.5 and 1.14.2, as follows:
> > [ ] +1, Approve the releases
> > [ ] -1, Do not approve the releases (please provide specific comments)
> >
> > The complete staging area is available for your review, which includes:
> > * JIRA release notes [1],
> > * the official Apache source releases and binary convenience releases
> > to be deployed to dist.apache.org [2], which are signed with the key
> > with fingerprint C2EED7B111D464BA [3],
> > * all artifacts to be deployed to the Maven Central Repository [4],
> > * source code tags [5],
> > * website pull request listing the new releases and adding
> > announcement blog post [6].
> >
> > The vote will be open for at least 24 hours. The minimum vote time has
> > been shortened as the changes are minimal and the matter is urgent.
> > It is adopted by majority approval, with at least 3 PMC affirmative
> > votes.
> >
> > Thanks,
> > Chesnay
> >
> > [1]
> > 1.11:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12351056
> > 1.12:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12351057
> > 1.13:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12351058
> > 1.14:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12351059
> > [2]
> > 1.11: https://dist.apache.org/repos/dist/dev/flink/flink-1.11.6-rc1/
> > 1.12: https://dist.apache.org/repos/dist/dev/flink/flink-1.12.7-rc1/
> > 1.13: https://dist.apache.org/repos/dist/dev/flink/flink-1.13.5-rc1/
> > 1.14: https://dist.apache.org/repos/dist/dev/flink/flink-1.14.2-rc1/
> > [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> > [4]
> > 1.11:
> > https://repository.apache.org/content/repositories/orgapacheflink-1460
> > 1.12:
> > https://repository.apache.org/content/repositories/orgapacheflink-1462
> > 1.13:
> > https://repository.apache.org/content/repositories/orgapacheflink-1459
> > 1.14:
> > https://repository.apache.org/content/repositories/orgapacheflink-1461
> > [5]
> > 1.11: https://github.com/apache/flink/releases/tag/release-1.11.6-rc1
> > 1.12: https://github.com/apache/flink/releases/tag/release-1.12.7-rc1
> > 1.13: https://github.com/apache/flink/releases/tag/release-1.13.5-rc1
> > 1.14: https://github.com/apache/flink/releases/tag/release-1.14.2-rc1
> > [6] https://github.com/apache/flink-web/pull/489
> >
> >
>
>

Re: [VOTE] FLIP-193: Snapshots ownership

[Yu Li]

+1

Thanks for the efforts Dawid!

Best Regards,
Yu


On Fri, 3 Dec 2021 at 16:20, Yun Tang  wrote:

> +1
>
> Thanks for driving this, Dawid.
>
> Best
> Yun Tang
> 
> From: Roman Khachatryan 
> Sent: Thursday, December 2, 2021 17:02
> To: dev 
> Subject: Re: [VOTE] FLIP-193: Snapshots ownership
>
> +1
>
> Thanks for driving this effort Dawid
>
> Regards,
> Roman
>
>
> On Wed, Dec 1, 2021 at 2:04 PM Konstantin Knauf  wrote:
> >
> > Thanks, Dawid.
> >
> > +1
> >
> > On Wed, Dec 1, 2021 at 1:23 PM Dawid Wysakowicz 
> > wrote:
> >
> > > Dear devs,
> > >
> > > I'd like to open a vote on FLIP-193: Snapshots ownership [1] which was
> > > discussed in this thread [2].
> > > The vote will be open for at least 72 hours unless there is an
> objection or
> > > not enough votes.
> > >
> > > Best,
> > >
> > > Dawid
> > >
> > > [1] https://cwiki.apache.org/confluence/x/bIyqCw
> > >
> > > [2] https://lists.apache.org/thread/zw2crf0c7t7t4cb5cwcwjpvsb3r1ovz2
> > >
> > >
> > >
> >
> > --
> >
> > Konstantin Knauf
> >
> > https://twitter.com/snntrable
> >
> > https://github.com/knaufk
>

Re: [ANNOUNCE] New Apache Flink Committer - Yingjie Cao

[Yu Li]

Congrats and welcome, Yingjie!

Best Regards,
Yu


On Thu, 18 Nov 2021 at 19:01, Yun Tang  wrote:

> Congratulations, Yinjie!
>
> Best
> Yun Tang
>
> On 2021/11/18 08:01:44 Martijn Visser wrote:
> > Congratulations!
> >
> > On Thu, 18 Nov 2021 at 02:44, Leonard Xu  wrote:
> >
> > > Congratulations！Yingjie
> > >
> > > Best，
> > > Leonard
> > >
> > > > 在 2021年11月18日，01:40，Till Rohrmann  写道：
> > > >
> > > > Congratulations Yingjie!
> > >
> > >
> >
>

Re: [ANNOUNCE] Documentation now available at nightlies.apache.org

[Yu Li]

Thank you all for the efforts! However, it seems to me that
https://flink.apache.org/docs/1.14/ will be redirected to
https://nightlies.apache.org/flink/flink-docs-master/1.14/ and get a 404
error. The correct link to redirect to should be
https://nightlies.apache.org/flink/flink-docs-release-1.14/. Would be great
if any of us could further correct this (I guess some regex correction
could do the trick), thanks!

Best Regards,
Yu


On Thu, 11 Nov 2021 at 15:26, David Morávek  wrote:

> Also big thanks to Gavin for setting the redirects up! ;)
>
> Best,
> D.
>
> On Thu, Nov 11, 2021 at 2:34 AM Leonard Xu  wrote:
>
> > Nice !
> > Thanks chesnay for the continuous effort.
> >
> > > 在 2021年11月11日，06:58，Chesnay Schepler  写道：
> > >
> > > A redirect from ci.apache.org to nightlies.apache.org has been set up.
> > >
> > > On 05/11/2021 04:44, Yun Tang wrote:
> > >> Hi Chesnay,
> > >>
> > >> It seems that the redirection has not been completed. As old
> > documentation hasn't updated for days, shall we add a waring on top of
> > documentation, like current warning of "This documentation is for an
> > out-of-date version of Apache Flink." to tell people to go to new
> location?
> > >>
> > >> Best
> > >> Yun Tang
> > >> 
> > >> From: Chesnay Schepler 
> > >> Sent: Friday, September 10, 2021 13:32
> > >> To: dev@flink.apache.org ; Leonard Xu <
> > xbjt...@gmail.com>
> > >> Subject: Re: [ANNOUNCE] Documentation now available at
> > nightlies.apache.org
> > >>
> > >> A redirection will be setup by infra at some point.
> > >>
> > >> On 10/09/2021 05:23, Leonard Xu wrote:
> > >>> Thanks Chesnay for the migration work.
> > >>>
> > >>> Should we add a redirection for the old documentation site:
> > https://ci.apache.org/flink/flink-docs-master/  to make
> > >>> it redirect to the new one:
> > https://nightlies.apache.org/flink/flink-docs-master/ ?
> > >>>
> > >>> The bookmark in users’ browser should still be the old one, I googled
> > "flink documents" which also returned the old one.
> > >>> And the old one won’t be updated and would be outdated soon.
> > >>>
> > >>> Best,
> > >>> Leonard
> > >>>
> >  在 2021年9月6日，17:11，Chesnay Schepler  写道：
> > 
> >  Website has been updated to point to nightlies.apache.org as well.
> > 
> >  On 03/09/2021 08:03, Chesnay Schepler wrote:
> > > The migration is pretty much complete and the documentation is now
> > available at nightlies.apache.org .
> > >
> > > Please click around a bit and check if anything is broken.
> > >
> > > If no issues are reported by the end of today I will update the
> > links on the website.
> > >
> > > On 01/09/2021 10:11, Chesnay Schepler wrote:
> > >> We are in the final steps of migrating the documentation to the
> new
> > buildbot setup.
> > >>
> > >> Because of that the documentation currently available at
> > ci.apache.org will NOT be updated until further notice because the old
> > builders have been deactivated while we iron out kinks in the new ones.
> > >>
> > >> I will keep you updated on the progress.
> > >>
> > >>
> > >
> >
> >
>

Re: [ANNOUNCE] New Apache Flink Committer - Yangze Guo

[Yu Li]

Congratulations, Yangze!

Best Regards,
Yu


On Mon, 15 Nov 2021 at 12:30, Rui Li  wrote:

> Congratulations Yangze!
>
> On Mon, Nov 15, 2021 at 11:44 AM wenlong.lwl 
> wrote:
>
> > Congratulations, Yangze!
> >
> > On Mon, 15 Nov 2021 at 10:37, Zhilong Hong  wrote:
> >
> > > Congratulations, Yangze!
> > >
> > > On Mon, Nov 15, 2021 at 10:13 AM Qingsheng Ren 
> > wrote:
> > >
> > > > Congratulations Yangze!
> > > >
> > > > --
> > > > Best Regards,
> > > >
> > > > Qingsheng Ren
> > > > Email: renqs...@gmail.com
> > > > On Nov 12, 2021, 10:11 AM +0800, Xintong Song  >,
> > > > wrote:
> > > > > Hi everyone,
> > > > >
> > > > > On behalf of the PMC, I'm very happy to announce Yangze Guo as a
> new
> > > > Flink
> > > > > committer.
> > > > >
> > > > > Yangze has been consistently contributing to this project for
> almost
> > 3
> > > > > years. His contributions are mainly in the resource management and
> > > > > deployment areas, represented by the fine-grained resource
> management
> > > and
> > > > > external resource framework. In addition to feature works, he's
> also
> > > > active
> > > > > in miscellaneous contributions, including PR reviews, document
> > > > enhancement,
> > > > > mailing list services and meetup/FF talks.
> > > > >
> > > > > Please join me in congratulating Yangze Guo for becoming a Flink
> > > > committer!
> > > > >
> > > > > Thank you~
> > > > >
> > > > > Xintong Song
> > > >
> > >
> >
>
>
> --
> Best regards!
> Rui Li
>

Re: [ANNOUNCE] New Apache Flink Committer - Leonard Xu

[Yu Li]

Congratulations, Leonard!

Best Regards,
Yu


On Mon, 15 Nov 2021 at 12:29, Rui Li  wrote:

> Congratulations Leonard!
>
> On Mon, Nov 15, 2021 at 11:44 AM wenlong.lwl 
> wrote:
>
> > Congratulations, Leonard!
> >
> > On Mon, 15 Nov 2021 at 10:43, Zhilong Hong  wrote:
> >
> > > Congratulations, Leonard!
> > >
> > > On Mon, Nov 15, 2021 at 10:13 AM Qingsheng Ren 
> > wrote:
> > >
> > > > Congratulations Leonard!
> > > >
> > > > --
> > > > Best Regards,
> > > >
> > > > Qingsheng Ren
> > > > Email: renqs...@gmail.com
> > > > On Nov 12, 2021, 12:12 PM +0800, Jark Wu , wrote:
> > > > > Hi everyone,
> > > > >
> > > > > On behalf of the PMC, I'm very happy to announce Leonard Xu as a
> new
> > > > Flink
> > > > > committer.
> > > > >
> > > > > Leonard has been a very active contributor for more than two year,
> > > > authored
> > > > > 150+ PRs and reviewed many PRs which is quite outstanding.
> > > > > Leonard mainly works on Flink SQL parts and drives several
> important
> > > > FLIPs,
> > > > > e.g. FLIP-132 (temporal table join) and FLIP-162 (correct time
> > > > behaviors).
> > > > > He is also the maintainer of flink-cdc-connectors[1] project which
> > > helps
> > > > a
> > > > > lot for users building a real-time data warehouse and data lake.
> > > > >
> > > > > Please join me in congratulating Leonard for becoming a Flink
> > > committer!
> > > > >
> > > > > Cheers,
> > > > > Jark Wu
> > > > >
> > > > > [1]: https://github.com/ververica/flink-cdc-connectors
> > > >
> > >
> >
>
>
> --
> Best regards!
> Rui Li
>

Re: Create a public open GitHub org for Flink ecosystem projects.

[Yu Li]

Thanks for driving this Becket, I like the idea and please feel free to
count me in as a maintainer (smile).

Best Regards,
Yu


On Thu, 23 Sept 2021 at 15:26, Leonard Xu  wrote:

> Thanks  Becket and PMC members for the effort.
>
> There’s one developer is willing to contribute MongoDB connector to
> community in user-zh mail list,
>  he has developed an internal version in their company, I think this
> project is pretty proper for such kind of contributions.
>
> Best,
> Leonard
> [1]
> https://lists.apache.org/thread.html/r82c376fea440100f1cb3050026afa07cdc99b94454f608e05e4102f1%40%3Cuser-zh.flink.apache.org%3E
>
> > 在 2021年9月23日，14:59，Ingo Bürk  写道：
> >
> > Hi,
> >
> > thank you (and the PMC) for the initiative on such a community effort.
> > Are there already projects expected/known to move to such an
> organization?
> > I think it would make sense to have at least a couple projects lined up
> so
> > the org doesn't start out empty.
> >
> >
> > Best
> > Ingo
> >
> > On Thu, Sep 23, 2021 at 8:43 AM Becket Qin  wrote:
> >
> >> Hi Flink devs,
> >>
> >> Recently we had some discussion in the Flink PMC about creating a public
> >> open GitHub organization to host the code repo of some Flink ecosystem
> >> projects. Instead of the Flink PMC doing this, we found that it is more
> >> suitable for someone in the Flink community to do this on their personal
> >> behalf. So here I would love to see if people would be interested in
> coming
> >> together to help create and maintain this GitHub organization as a
> >> community effort.
> >>
> >> *** Motivation*
> >>
> >> Currently, usually an ecosystem project is hosted in a company's GitHub
> >> repo. However, this does not always work well for those who want to
> >> collaborate on the projects..
> >>
> >>   1. Some employers may have concerns if their employees contribute code
> >>   to another company's repo. Instead, they would rather fork and develop
> >> in
> >>   their own repo. This results in split efforts instead of joint force
> to
> >>   develop the project.
> >>   2. Sometimes a company's policy disallows granting repo permissions to
> >>   external contributors.
> >>   3. Sometimes a company does not have a GitHub repo and is also not
> >>   willing to open source a project in a personal repo.
> >>
> >> Therefore a public open GitHub organization would provide a *neutral*
> place
> >> helpful to facilitate the sharing and collaboration on the Flink
> ecosystem
> >> projects for developers in these situations.
> >>
> >> *** How does it work?*
> >>
> >>   1. The public ecosystem GitHub org would be created and maintained by
> a
> >>   few volunteers.
> >>   2. The volunteers who maintain the org are only responsible for
> creating
> >>   and deleting the individual project code repositories upon the
> requests
> >>   from the project owners.
> >>   3. When someone wants to put a Flink ecosystem project in this
> >>   organization, a new GitHub repo will be created to host that project.
> >>   4. The owners of each individual project will maintain the code repo
> of
> >>   that project, including merging PRs, granting commit permissions to
> >> other
> >>   contributors, publishing releases, etc.
> >>
> >> *Note that this open GitHub org is NOT affiliated with ASF or the Apache
> >> Flink project, although the volunteers who maintain the org may be Flink
> >> committers or PMC members.*
> >>
> >> *** What's next*
> >> If people find the public GitHub org for the ecosystem projects useful,
> we
> >> will do the following:
> >>
> >>   1. Create the org together with the volunteers helping maintain the
> org.
> >>   (PMC permission is required if the org name contains "Flink", which is
> >>   likely).
> >>   2. Welcome people to put their projects in the org as they see fit.
> >>   3. Link the projects to flink-packages.org
> >>
> >>
> >> To give some additional context, the following questions were raised and
> >> answered in the earlier PMC discussion.
> >> *** Why not host the projects in Apache?*
> >> One suggestion brought up was asking the ecosystem project owners to
> >> contribute their projects to Apache, either to an existing project such
> as
> >> Apache Bahir, or through the incubator.
> >>
> >> The ASF is a great place to host organization neutral projects. However,
> >> being a part of an Apache project has a high standard and demands long
> term
> >> commitments. People also have to be committers, use jira, mailing lists.
> >> The projects might also have to go through incubation which is even more
> >> involved.
> >>
> >> Some of the ecosystem projects might not be ready to become a part of
> >> Apache in some cases. The project may still be in the starting stage and
> >> people don't know if it will last. Some of the projects may want more
> >> flexible coordination, etc.
> >>
> >> Therefore, an open GitHub organization would solve the issues mentioned
> in
> >> the motivation with the least restrictions.
> >>
> >> *** The relationship with 

Re: [ANNOUNCE] Apache Flink 1.13.2 released

[Yu Li]

Thanks Yun Tang for being our release manager and everyone else who made
the release possible!

Best Regards,
Yu


On Fri, 6 Aug 2021 at 13:52, Yun Tang  wrote:

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

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

[Yu Li]

+1 (binding)

- Checked the diff between 1.12.4 and 1.12.5-rc3: OK (
https://github.com/apache/flink/compare/release-1.12.4...release-1.12.5-rc3)
  - commons-io version has been bumped to 2.8.0 through FLINK-22747 and all
NOTICE files updated correctly
  - guava version has been bumped to 29.0 for kinesis connector through
FLINK-23009 and all NOTICE files updated correctly
- Checked release notes: OK
  - minor: I've moved FLINK-23577 out of 1.12.5
- Checked sums and signatures: OK
- Maven clean install from source: OK
- Checked the jars in the staging repo: OK
- Checked the website updates: Changes Required
  - Note: release note needs update but is not a blocker for the RC

Best Regards,
Yu


On Mon, 2 Aug 2021 at 12:25, JING ZHANG  wrote:

> +1 (non-binding)
>
> 1. built from source code flink-1.12.5-bin-scala_2.11.tgz
> <
> https://dist.apache.org/repos/dist/dev/flink/flink-1.12.5-rc3/flink-1.12.5-bin-scala_2.11.tgz
> >
> succeeded
> 2. Started a local Flink cluster, ran the WordCount example, WebUI looks
> good,  no suspicious output/log
> 3. started cluster and run some e2e sql queries using SQL Client, query
> result is expected. (Find a minor bug  FLINK-23554
>  which would happen in
> some corner cases, so it is not a blocker)
> 4. Repeat Step 2 and 3 with flink-1.12.5-src.tgz
> <
> https://dist.apache.org/repos/dist/dev/flink/flink-1.12.5-rc3/flink-1.12.5-src.tgz
> >
>
> Best,
> JING ZHANG
>
> Dian Fu  于2021年8月2日周一 上午9:59写道：
>
> > +1 (binding)
> >
> > -  checked the website PR
> > -  verified the signatures and checksum
> > -  Installed the Python wheel package of Python 3.8 on MacOS and runs
> some
> > simple examples
> >
> > Regards,
> > Dian
> >
> > > 2021年8月1日 下午3:32，Leonard Xu  写道：
> > >
> > > +1 (non-binding)
> > >
> > > - verified signatures and hashsums
> > > - checked all dependency artifacts are 1.12.5
> > > - started a cluster, ran a wordcount job, the result is expected, no
> > suspicious log output
> > > - started SQL Client, ran some sql queries in SQL Client, the result is
> > expected, no suspicious log output
> > > - reviewed the web PR
> > >
> > > Best,
> > > Leonard
> > >
> > >> 在 2021年8月1日，15:24，Jark Wu  写道：
> > >>
> > >> +1 (binding)
> > >>
> > >> - checked/verified signatures and hashes
> > >> - started cluster, ran examples, verified web ui and log output,
> nothing
> > >> unexpected
> > >> - started cluster and ran some e2e sql queries using sql-client, looks
> > good:
> > >> - read from kafka source, aggregate, write into mysql
> > >> - read from kafka source with watermark defined in ddl, window
> > aggregate,
> > >> write into mysql
> > >> - read from kafka with computed column defined in ddl, temporal join
> > with
> > >> a mysql table, write into kafka
> > >> - reviewed the release PR
> > >>
> > >> Best,
> > >> Jark
> > >>
> > >> On Sat, 31 Jul 2021 at 10:22, godfrey he  wrote:
> > >>
> > >>> +1 (non-binding)
> > >>>
> > >>> - Checked checksums and signatures: OK
> > >>> - Built from source: OK
> > >>> - Checked the flink-web PR
> > >>>  - find one typo about flink version
> > >>> - Submit some jobs from sql-client to local cluster, checked the
> > web-ui,
> > >>> cp, sp, log, etc: OK
> > >>>
> > >>> Best,
> > >>> Godfrey
> > >>>
> > >>> Robert Metzger  于2021年7月30日周五 下午4:33写道：
> > >>>
> >  Thanks a lot for providing the new staging repository. I dropped the
> > 1440
> >  and 1441 staging repositories, to avoid that other RC reviewers
> >  accidentally look into it, or that we accidentally release it.
> > 
> >  +1 (binding)
> > 
> >  Checks:
> >  - I didn't find any additional issues in the release announcement
> >  - the pgp signatures on the source archive seem fine
> >  - source archive compilation starts successfully (rat check passes
> > etc.)
> >  - standalone mode, job submission and cli cancellation works. logs
> > look
> >  fine
> >  - maven staging repository looks fine
> > 
> >  On Fri, Jul 30, 2021 at 7:30 AM Jingsong Li  >
> >  wrote:
> > 
> > > Hi everyone,
> > >
> > > Thanks Robert, I created a new one.
> > >
> > > all artifacts to be deployed to the Maven Central Repository [4],
> > >
> > > [4]
> > >
> > >>>
> > https://repository.apache.org/content/repositories/orgapacheflink-1444/
> > >
> > > Best,
> > > Jingsong
> > >
> > > On Thu, Jul 29, 2021 at 9:50 PM Robert Metzger <
> rmetz...@apache.org>
> > > wrote:
> > >
> > >> The difference is that the 1440 staging repository contains the
> > Scala
> > > _2.11
> > >> files, the 1441 repo contains scala_2.12. I'm not sure if this
> > works,
> > >> because things like "flink-core:1.11.5" will be released twice?
> > >> I would prefer to have a single staging repository containing all
> > > binaries
> > >> we intend to release to maven central, to avoid complications in
> the
> > >> release process.
> > 

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

[Yu Li]

+1 (binding)

- Checked the diff between 1.11.3 and 1.11.4-rc1: OK (
https://github.com/apache/flink/compare/release-1.11.3...release-1.11.4-rc1)
  - jackson version has been bumped to 2.10.5.1 through FLINK-21020 and all
NOTICE files updated correctly
  - beanutils version has been bumped to 1.9.4 through FLINK-21123 and all
NOTICE files updated correctly
  - snappy-java version has been bumped to 1.1.8.3 through FLINK-22208 and
all NOTICE files updated correctly
  - aws sdk version has been bumped to 1.12.7 for kinesis connector through
FLINK-18182 and all NOTICE files updated correctly
  - guava version has been bumped to 29.0 for kinesis connector through
FLINK-18182 and all NOTICE files updated correctly
- Checked release notes: OK
- Checked sums and signatures: OK
- Maven clean install from source: OK
- Checked the jars in the staging repo: OK
- Checked the website updates: Changes Required
  - Note: necessary changes needed before merging, but this is not a
blocker for RC

Best Regards,
Yu


On Mon, 2 Aug 2021 at 10:22, Dian Fu  wrote:

> +1 (binding)
>
> -  checked the website PR
> -  verified the signatures and checksum
> -  installed the Python wheel package of Python 3.7 on MacOS and runs the
> word count example
>
> Regards,
> Dian
>
> > 2021年8月1日 下午4:17，Leonard Xu  写道：
> >
> > +1 (non-binding)
> >
> > - verified signatures and hashsums
> > - built from source code with scala 2.11 succeeded
> > - checked all dependency artifacts are 1.11.4
> > - started a cluster, ran a wordcount job, the result is expected, no
> suspicious log output
> > - started SQL Client, ran some SQL queries, the result is expected
> > - reviewed the web PR
> >
> > Best,
> > Leonard
> >
> >> 在 2021年7月26日，23:25，godfrey he  写道：
> >>
> >> Hi everyone,
> >> Please review and vote on the release candidate #1 for the version
> 1.11.4,
> >> as follows:
> >> [ ] +1, Approve the release
> >> [ ] -1, Do not approve the release (please provide specific comments)
> >>
> >>
> >> The complete staging area is available for your review, which includes:
> >> * JIRA release notes [1],
> >> * the official Apache source release and binary convenience releases to
> be
> >> deployed to dist.apache.org [2], which are signed with the key with
> >> fingerprint 4A978875E56AA2100EB0CF12A244D52CF0A40279 [3],
> >> * all artifacts to be deployed to the Maven Central Repository [4],
> >> * source code tag "release-1.11.4-rc1" [5],
> >> * website pull request listing the new release and adding announcement
> blog
> >> post [6].
> >>
> >> The vote will be open for at least 72 hours. It is adopted by majority
> >> approval, with at least 3 PMC affirmative votes.
> >>
> >> Best,
> >> Godfrey
> >>
> >> [1]
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12349404
> >> [2] https://dist.apache.org/repos/dist/dev/flink/flink-1.11.4-rc1/
> >> [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> >> [4]
> https://repository.apache.org/content/repositories/orgapacheflink-1438
> >> [5] https://github.com/apache/flink/releases/tag/release-1.11.4-rc1
> >> [6] https://github.com/apache/flink-web/pull/459
> >
>
>

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

[Yu Li]

+1 (binding)

- Checked the diff between 1.13.1 and 1.13.2-rc3: OK (
https://github.com/apache/flink/compare/release-1.13.1...release-1.13.2-rc3)
  - commons-io version has been bumped to 2.8.0 through FLINK-22747 and all
NOTICE files updated correctly
  - guava version has been bumped to 29.0 for kinesis connector through
FLINK-23009 and all NOTICE files updated correctly
- Checked release notes: OK
  - minor: I've moved FLINK-23315 and FLINK-23418 out of 1.13.2 to keep
accordance with RC status
- Checked sums and signatures: OK
- Maven clean install from source: OK
- Checked the jars in the staging repo: OK
- Checked the website updates: OK
  - minor: left some minor comments in PR (such as RN needs update, etc.)
and please remember to address them before merging

Best Regards,
Yu


On Fri, 30 Jul 2021 at 14:00, Jingsong Li  wrote:

> +1 (non-binding)
>
> - Check if checksums and GPG files match the corresponding release files
> - staging repository looks fine
> - Start a local cluster (start-cluster.sh), logs fine
> - Run sql-client and run a job, looks fine
>
> I found an unexpected log in sql-client:
> "Searching for
>
> '/Users/lijingsong/Downloads/tmp/flink-1.13.2/conf/sql-client-defaults.yaml'...not
> found"
> This log should be removed. I created a JIRA for this:
> https://issues.apache.org/jira/browse/FLINK-23552
> (This should not be a blocker)
>
> Best,
> Jingsong
>
> On Thu, Jul 29, 2021 at 10:44 PM Robert Metzger 
> wrote:
>
> > Thanks a lot for creating this release candidate
> >
> > +1 (binding)
> >
> > - staging repository looks fine
> > - Diff to 1.13.1 looks fine wrt to dependency changes:
> >
> https://github.com/apache/flink/compare/release-1.13.1...release-1.13.2-rc3
> > - standalone mode works locally
> >- I found this issue, which is not specific to 1.13.2:
> > https://issues.apache.org/jira/browse/FLINK-23546
> > - src archive signature is matched; sha512 is correct
> >
> > On Thu, Jul 29, 2021 at 9:10 AM Zakelly Lan 
> wrote:
> >
> > > +1 (non-binding)
> > >
> > > * Built from source.
> > > * Run wordcount datastream job on yarn
> > > * Web UI and checkpoint seem good.
> > > * Kill a container to make job failover, everything is good.
> > > * Try run job from checkpoint, everything is good.
> > >
> > > On Fri, Jul 23, 2021 at 10:04 PM Yun Tang  wrote:
> > >
> > > > Hi everyone,
> > > > Please review and vote on the release candidate #3 for the version
> > > 1.13.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 78A306590F1081CC6794DC7F62DAD618E07CF996 [3],
> > > > * all artifacts to be deployed to the Maven Central Repository [4],
> > > > * source code tag "release-1.13.2-rc3" [5],
> > > > * website pull request listing the new release and adding
> announcement
> > > > blog post [6].
> > > >
> > > > The vote will be open for at least 72 hours. It is adopted by
> majority
> > > > approval, with at least 3 PMC affirmative votes.
> > > >
> > > > Best,
> > > > Yun Tang
> > > >
> > > > [1]
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12350218==12315522
> > > > [2] https://dist.apache.org/repos/dist/dev/flink/flink-1.13.2-rc3/
> > > > [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> > > > [4]
> > > >
> > https://repository.apache.org/content/repositories/orgapacheflink-1439/
> > > > [5] https://github.com/apache/flink/releases/tag/release-1.13.2-rc3
> > > > [6] https://github.com/apache/flink-web/pull/453
> > > >
> > > >
> > >
> >
>
>
> --
> Best, Jingsong Lee
>

Re: [RESULT] [VOTE] FLIP-172: Support custom transactional.id prefix in FlinkKafkaProducer

[Yu Li]

Good to know the result and thanks for driving this, Wenhao.

Minor: according to the Flink bylaw [1] and recent announcement [2], Yuan
Mei's vote is binding.

Best Regards,
Yu

[1]
https://cwiki.apache.org/confluence/display/FLINK/Flink+Bylaws#FlinkBylaws-Actions
[2] https://s.apache.org/99bg2


On Sat, 10 Jul 2021 at 12:24, Wenhao Ji  wrote:

> Hi everyone,
>
> I am happy to announce that FLIP-172 [1] is approved. The vote [2] is
> now closed.
>
> There were five +1 votes, three of them were binding:
> - Dawid Wysakowicz (binding)
> - Piotr Nowojski (binding)
> - Arvid Heise (binding)
> - Yuan Mei (non-binding)
> - Daniel Lorych (non-binding)
>
> There was no veto.
>
> Thank everyone for participating!
>
> [1]
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-172%3A+Support+custom+transactional.id+prefix+in+FlinkKafkaProducer
> [2]
> https://lists.apache.org/thread.html/r5c69f2f8467637290b3607fdbb8e7e2b59be54705e3d22ec5d123683%40%3Cdev.flink.apache.org%3E
>
> Wenhao
>

[ANNOUNCE] New Apache Flink Committer - Yuan Mei

[Yu Li]

Hi all,

On behalf of the PMC, I’m very happy to announce Yuan Mei as a new Flink
committer.

Yuan has been an active contributor for more than two years, with code
contributions on multiple components including kafka connectors,
checkpointing, state backends, etc. Besides, she has been actively involved
in community activities such as helping manage releases, discussing
questions on dev@list, supporting users and giving talks at conferences.

Please join me in congratulating Yuan for becoming a Flink committer!

Cheers,
Yu

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

[Yu Li]

Congrats and welcome, Yang!

Best Regards,
Yu


On Wed, 7 Jul 2021 at 10:57, Yuan Mei  wrote:

> Congratulations, Yang!
>
> Best
> Yuan
>
> On Wed, Jul 7, 2021 at 10:47 AM Jary Zhen  wrote:
>
> > Congratulations, Yang Wang.
> >
> > Best
> > Jary
> >
> > Yun Gao  于2021年7月7日周三 上午10:38写道：
> >
> > > Congratulations Yang!
> > >
> > > Best,
> > > Yun
> > >
> > >
> > > --
> > > Sender:Jark Wu
> > > Date:2021/07/07 10:20:27
> > > Recipient:dev
> > > Cc:Yang Wang; 
> > > Theme:Re: [ANNOUNCE] New Apache Flink Committer - Yang Wang
> > >
> > > Congratulations Yang Wang!
> > >
> > > Best,
> > > Jark
> > >
> > > On Wed, 7 Jul 2021 at 10:09, Xintong Song 
> wrote:
> > >
> > > > Hi everyone,
> > > >
> > > > On behalf of the PMC, I'm very happy to announce Yang Wang as a new
> > Flink
> > > > committer.
> > > >
> > > > Yang has been a very active contributor for more than two years,
> mainly
> > > > focusing on Flink's deployment components. He's a main contributor
> and
> > > > maintainer of Flink's native Kubernetes deployment and native
> > Kubernetes
> > > > HA. He's also very active on the mailing lists, participating in
> > > > discussions and helping with user questions.
> > > >
> > > > Please join me in congratulating Yang Wang for becoming a Flink
> > > committer!
> > > >
> > > > Thank you~
> > > >
> > > > Xintong Song
> > > >
> > >
> > >
> >
>

Re: Re: [ANNOUNCE] New PMC member: Guowei Ma

[Yu Li]

Congrats and welcome, Guowei!

Best Regards,
Yu


On Wed, 7 Jul 2021 at 10:56, Yuan Mei  wrote:

> Congratulations Guowei!
>
> Best,
> Yuan
>
> On Wed, Jul 7, 2021 at 10:49 AM Jary Zhen  wrote:
>
> > Congratulations Guowei!
> >
> >
> > Best,
> > Jary
> >
> > Yun Gao  于2021年7月7日周三 上午10:38写道：
> >
> > > Congratulations Guowei!
> > >
> > >
> > > Best,
> > > Yun
> > >
> > >
> > > --
> > > Sender:JING ZHANG
> > > Date:2021/07/07 10:33:51
> > > Recipient:dev
> > > Theme:Re: [ANNOUNCE] New PMC member: Guowei Ma
> > >
> > > Congratulations,  Guowei Ma!
> > >
> > > Best regards,
> > > JING ZHANG
> > >
> > > Zakelly Lan  于2021年7月7日周三 上午10:30写道：
> > >
> > > > Congratulations, Guowei!
> > > >
> > > > Best,
> > > > Zakelly
> > > >
> > > > On Wed, Jul 7, 2021 at 10:24 AM tison  wrote:
> > > >
> > > > > Congrats! NB.
> > > > >
> > > > > Best,
> > > > > tison.
> > > > >
> > > > >
> > > > > Jark Wu  于2021年7月7日周三 上午10:20写道：
> > > > >
> > > > > > Congratulations Guowei!
> > > > > >
> > > > > > Best,
> > > > > > Jark
> > > > > >
> > > > > > On Wed, 7 Jul 2021 at 09:54, XING JIN 
> > > wrote:
> > > > > >
> > > > > > > Congratulations, Guowei~ !
> > > > > > >
> > > > > > > Best,
> > > > > > > Jin
> > > > > > >
> > > > > > > Xintong Song  于2021年7月7日周三 上午9:37写道：
> > > > > > >
> > > > > > > > Congratulations, Guowei~!
> > > > > > > >
> > > > > > > > Thank you~
> > > > > > > >
> > > > > > > > Xintong Song
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On Wed, Jul 7, 2021 at 9:31 AM Qingsheng Ren <
> > renqs...@gmail.com
> > > >
> > > > > > wrote:
> > > > > > > >
> > > > > > > > > Congratulations Guowei!
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > Best Regards,
> > > > > > > > >
> > > > > > > > > Qingsheng Ren
> > > > > > > > > Email: renqs...@gmail.com
> > > > > > > > > 2021年7月7日 +0800 09:30 Leonard Xu ，写道：
> > > > > > > > > > Congratulations! Guowei Ma
> > > > > > > > > >
> > > > > > > > > > Best,
> > > > > > > > > > Leonard
> > > > > > > > > >
> > > > > > > > > > > ÔÚ 2021Äê7ÔÂ6ÈÕ£¬21:56£¬Kurt Young 
> > > дµÀ£º
> > > > > > > > > > >
> > > > > > > > > > > Hi all!
> > > > > > > > > > >
> > > > > > > > > > > I'm very happy to announce that Guowei Ma has joined
> the
> > > > Flink
> > > > > > PMC!
> > > > > > > > > > >
> > > > > > > > > > > Congratulations and welcome Guowei!
> > > > > > > > > > >
> > > > > > > > > > > Best,
> > > > > > > > > > > Kurt
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > >
> >
>

Re: Flink 1.14. Bi-weekly 2021-06-22

[Yu Li]

Thanks for taking care of this, Joe! The information is very helpful!

Best Regards,
Yu


On Mon, 28 Jun 2021 at 18:40, Till Rohrmann  wrote:

> Thanks a lot for the update, Joe. This is very helpful!
>
> Cheers,
> Till
>
> On Mon, Jun 28, 2021 at 10:10 AM Xintong Song 
> wrote:
>
> > Thanks for the update, Joe.
> >
> > Thank you~
> >
> > Xintong Song
> >
> >
> > On Mon, Jun 28, 2021 at 3:54 PM Johannes Moser 
> > wrote:
> >
> > > Hello,
> > >
> > > Last Tuesday was our second bi-weekly.
> > >
> > > You can read up the outcome in the confluence wiki page [1].
> > >
> > > *Feature freeze date*
> > > As we didn't come to a clear agreement, we will keep the anticipated
> > > feature freeze date
> > > as it is at early August.
> > >
> > > *Build stability*
> > > The good thing: we decreased the number of issues, the not so good
> thing:
> > > only by ten.
> > > We as a community need to put further effort into this.
> > >
> > > *Dependencies*
> > > We'd like to ask all contributors to have a look at the components they
> > > are heavily
> > > Involved with to see if any dependencies require updating. There were
> > some
> > > Issues recently to pass the security scans by some of the users. In
> > future
> > > this should
> > > somehow be a default at the beginning of every release cycle.
> > >
> > > *Criteria for merging PRs*
> > > We want to avoid merging PRs with unrelated CI failures. We are quite
> > > aware that we
> > > need to raise the importance of the Docker caching issue.
> > >
> > > What can you do to make the Flink 1.14. release a good one:
> > > * Identify and update outdated dependencies
> > > * Get rid of test instabilities
> > > * Don't merge PRs including unrelated CI failures
> > >
> > > Best,
> > > Joe
> > >
> > >
> > > [1] https://cwiki.apache.org/confluence/display/FLINK/1.14+Release
> >
>

Re: [ANNOUNCE] New PMC member: Arvid Heise

[Yu Li]

Congratulations, Arvid!

Best Regards,
Yu


On Thu, 24 Jun 2021 at 22:03, Yuan Mei  wrote:

> Congratulations Arvid !
>
> On Thu, Jun 24, 2021 at 8:03 PM Etienne Chauchot 
> wrote:
>
> > Congratulations Arvid !
> >
> > Etienne
> >
> > On 24/06/2021 12:04, Lijie Wang wrote:
> > > Congratulations!
> > >
> > > Igal Shilman  于2021年6月24日周四 下午5:46写道：
> > >
> > >> Congratulations Arvid!
> > >> Super well deserved!
> > >>
> > >>
> > >> On Thu, Jun 24, 2021 at 11:33 AM 刘建刚 
> wrote:
> > >>
> > >>> Congratulations
> > >>>
> > >>> Best
> > >>> liujiangang
> > >>>
> > >>> Matthias Pohl  于2021年6月23日周三 下午2:11写道：
> > >>>
> >  Congratulations, Arvid! :-)
> > 
> >  On Thu, Jun 17, 2021 at 9:02 AM Arvid Heise 
> wrote:
> > 
> > > Thank you for your trust and support.
> > >
> > > Arvid
> > >
> > > On Thu, Jun 17, 2021 at 8:39 AM Roman Khachatryan <
> ro...@apache.org>
> > > wrote:
> > >
> > >> Congratulations!
> > >>
> > >> Regards,
> > >> Roman
> > >>
> > >> On Thu, Jun 17, 2021 at 5:56 AM Xingbo Huang 
> >  wrote:
> > >>> Congratulations, Arvid!
> > >>>
> > >>> Best,
> > >>> Xingbo
> > >>>
> > >>> Yun Tang  于2021年6月17日周四 上午10:49写道：
> > >>>
> >  Congratulations, Arvid
> > 
> >  Best
> >  Yun Tang
> >  
> >  From: Yun Gao 
> >  Sent: Thursday, June 17, 2021 10:46
> >  To: Jingsong Li ; dev <
> >  dev@flink.apache.org>
> >  Subject: Re: Re: [ANNOUNCE] New PMC member: Arvid Heise
> > 
> >  Congratulations, Arvid!
> > 
> >  Best,
> >  Yun
> > 
> > 
> > 
> > >>> --
> >  Sender:Jingsong Li
> >  Date:2021/06/17 10:41:29
> >  Recipient:dev
> >  Theme:Re: [ANNOUNCE] New PMC member: Arvid Heise
> > 
> >  Congratulations, Arvid!
> > 
> >  Best,
> >  Jingsong
> > 
> >  On Thu, Jun 17, 2021 at 6:52 AM Matthias J. Sax <
> > >>> mj...@apache.org>
> > >> wrote:
> > > Congrats!
> > >
> > > On 6/16/21 6:06 AM, Leonard Xu wrote:
> > >> Congratulations, Arvid!
> > >>
> > >>
> > >>> 在 2021年6月16日，20:08，Till Rohrmann 
> > >> 写道：
> > >>> Congratulations, Arvid!
> > >>>
> > >>> Cheers,
> > >>> Till
> > >>>
> > >>> On Wed, Jun 16, 2021 at 1:47 PM JING ZHANG <
> > > beyond1...@gmail.com>
> > > wrote:
> >  Congratulations, Arvid!
> > 
> >  Nicholas Jiang  于2021年6月16日周三
> > >>> 下午7:25写道：
> > > Congratulations, Arvid!
> > >
> > >
> > >
> > > --
> > > Sent from:
> > > http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/
> > 
> >  --
> >  Best, Jingsong Lee
> > 
> > 
> >
>

Re: [DISCUSS] Do not merge PRs with "unrelated" test failures.

[Yu Li]

+1 for Xintong's proposal.

For me, resolving problems directly (fixing the infrastructure issue,
disabling unstable tests and creating blocker JIRAs to track the fix and
re-enable them asap, etc.) is (in most cases) better than working around
them (verify locally, manually check and judge the failure as "unrelated",
etc.), and I believe the proposal could help us pushing those more "real"
solutions forward.

Best Regards,
Yu


On Fri, 25 Jun 2021 at 10:58, Yangze Guo  wrote:

> Creating a blocker issue for the manually disabled tests sounds good to me.
>
> Minor: I'm still a bit worried about the commits merged before we fix
> the unstable tests can also break those tests. Instead of letting the
> assigners keep a look at all potentially related commits, they can
> maintain a branch that is periodically synced with the master branch
> while enabling the unstable test. So that they can catch the breaking
> changes asap.
>
> Best,
> Yangze Guo
>
> On Thu, Jun 24, 2021 at 9:52 PM Till Rohrmann 
> wrote:
> >
> > I like the idea of creating a blocker issue for a disabled test. This
> will
> > force us to resolve it in a timely manner and it won't fall through the
> > cracks.
> >
> > Cheers,
> > Till
> >
> > On Thu, Jun 24, 2021 at 8:06 AM Jingsong Li 
> wrote:
> >
> > > +1 to Xintong's proposal
> > >
> > > I also have some concerns about unstable cases.
> > >
> > > I think unstable cases can be divided into these types:
> > >
> > > - Force majeure: For example, network timeout, sudden environmental
> > > collapse, they are accidental and can always be solved by triggering
> azure
> > > again. Committers should wait for the next green azure.
> > >
> > > - Obvious mistakes: For example, some errors caused by obvious reasons
> may
> > > be repaired quickly. At this time, do we need to wait, or not wait and
> just
> > > ignore?
> > >
> > > - Difficult questions: These problems are very difficult to find. There
> > > will be no solution for a while and a half. We don't even know the
> reason.
> > > At this time, we should ignore it. (Maybe it's judged by the author of
> the
> > > case. But what about the old case whose author can't be found?)
> > >
> > > So, the ignored cases should be the block of the next release until the
> > > reason is found or the case is fixed?  We need to ensure that someone
> will
> > > take care of these cases, because there is no deepening of failed
> tests, no
> > > one may continue to pay attention to these cases.
> > >
> > > I think this guideline should consider these situations, and show how
> to
> > > solve them.
> > >
> > > Best,
> > > Jingsong
> > >
> > > On Thu, Jun 24, 2021 at 10:57 AM Jark Wu  wrote:
> > >
> > > > Thanks to Xintong for bringing up this topic, I'm +1 in general.
> > > >
> > > > However, I think it's still not very clear how we address the
> unstable
> > > > tests.
> > > > I think this is a very important part of this new guideline.
> > > >
> > > > According to the discussion above, if some tests are unstable, we can
> > > > manually disable it.
> > > > But I have some questions in my mind:
> > > > 1) Is the instability judged by the committer themselves or by some
> > > > metrics?
> > > > 2) Should we log the disable commit in the corresponding issue and
> > > increase
> > > > the priority?
> > > > 3) What if nobody looks into this issue and this becomes some
> potential
> > > > bugs released with the new version?
> > > > 4) If no person is actively working on the issue, who should
> re-enable
> > > it?
> > > > Would it block PRs again?
> > > >
> > > >
> > > > Best,
> > > > Jark
> > > >
> > > >
> > > > On Thu, 24 Jun 2021 at 10:04, Xintong Song 
> > > wrote:
> > > >
> > > > > Thanks all for the feedback.
> > > > >
> > > > > @Till @Yangze
> > > > >
> > > > > I'm also not convinced by the idea of having an exception for local
> > > > builds.
> > > > > We need to execute the entire build (or at least the failing stage)
> > > > > locally, to make sure subsequent test cases prevented by the
> failure
> > > one
> > > > > are all executed. In that case, it's probably easier to rerun the
> build
> > > > on
> > > > > azure than locally.
> > > > >
> > > > > Concerning disabling unstable test cases that regularly block PRs
> from
> > > > > merging, maybe we can say that such cases can only be disabled when
> > > > someone
> > > > > is actively looking into it, likely the person who disabled the
> case.
> > > If
> > > > > this person is no longer actively working on it, he/she should
> enable
> > > the
> > > > > case again no matter if it is fixed or not.
> > > > >
> > > > > @Jing
> > > > >
> > > > > Thanks for the suggestions.
> > > > >
> > > > > +1 to provide guidelines on handling test failures.
> > > > >
> > > > > 1. Report the test failures in the JIRA.
> > > > > >
> > > > >
> > > > > +1 on this. Currently, the release managers are monitoring the ci
> and
> > > > cron
> > > > > build instabilities and reporting them on JIRA. We should also
> > > encourage
> > > > > 

Re: Re: [ANNOUNCE] New PMC member: Xintong Song

[Yu Li]

Congratulations, Xintong!

Best Regards,
Yu


On Thu, 17 Jun 2021 at 15:23, Yuan Mei  wrote:

> Congratulations, Xintong :-)
>
> On Thu, Jun 17, 2021 at 11:57 AM Xingbo Huang  wrote:
>
> > Congratulations, Xintong!
> >
> > Best,
> > Xingbo
> >
> > Yun Gao  于2021年6月17日周四 上午10:46写道：
> >
> > > Congratulations, Xintong!
> > >
> > > Best,
> > > Yun
> > >
> > >
> > > --
> > > Sender:Jingsong Li
> > > Date:2021/06/17 10:41:22
> > > Recipient:dev
> > > Theme:Re: [ANNOUNCE] New PMC member: Xintong Song
> > >
> > > Congratulations, Xintong!
> > >
> > > Best,
> > > Jingsong
> > >
> > > On Thu, Jun 17, 2021 at 10:26 AM Yun Tang  wrote:
> > >
> > > > Congratulations, Xintong!
> > > >
> > > > Best
> > > > Yun Tang
> > > > 
> > > > From: Leonard Xu 
> > > > Sent: Wednesday, June 16, 2021 21:05
> > > > To: dev (dev@flink.apache.org) 
> > > > Subject: Re: [ANNOUNCE] New PMC member: Xintong Song
> > > >
> > > >
> > > > Congratulations, Xintong!
> > > >
> > > >
> > > > Best,
> > > > Leonard
> > > > > 在 2021年6月16日，20:07，Till Rohrmann  写道：
> > > > >
> > > > > Congratulations, Xintong!
> > > > >
> > > > > Cheers,
> > > > > Till
> > > > >
> > > > > On Wed, Jun 16, 2021 at 1:47 PM JING ZHANG 
> > > wrote:
> > > > >
> > > > >> Congratulations, Xintong!
> > > > >>
> > > > >>
> > > > >> Jiayi Liao  于2021年6月16日周三 下午7:30写道：
> > > > >>
> > > > 
> > > >  <
> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/>
> > > >  Congratulations Xintong!
> > > > 
> > > >  On Wed, Jun 16, 2021 at 7:24 PM Nicholas Jiang <
> > programg...@163.com
> > > >
> > > >  wrote:
> > > > 
> > > > > Congratulations, Xintong!
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Sent from:
> > > > >
> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/
> > > > 
> > > > 
> > > > >>>
> > > > >>
> > > >
> > > >
> > >
> > > --
> > > Best, Jingsong Lee
> > >
> > >
> >
>

Re: [DISCUSS][Statebackend][Runtime] Changelog Statebackend Configuration Proposal

[Yu Li]

+1 for option 3.

IMHO persisting (operator's) state data through change log is an
independent mechanism which could co-work with all kinds of local state
stores (heap and rocksdb). This mechanism is similar to the WAL
(write-ahead-log) mechanism in the database system. Although implement-wise
we're using wrapper (decorator) pattern and naming it as
`ChangeLogStateBackend`, it's not really another type of state backend. For
the same reason, ChangeLogStateBackend should be an internal class and not
exposed to the end user. Users only need to know / control whether to
enable change log or not, just like whether to enable WAL in the
traditional database system.

Thanks.

Best Regards,
Yu


On Thu, 3 Jun 2021 at 22:50, Piotr Nowojski  wrote:

> Hi,
>
> I would actually prefer option 6 (or 5/4), for the sake of configuration
> being explicit and self explanatory. But at the same time I don't have very
> hard preferences and from the remaining options, option 3 seems the most
> reasonable.
>
> The question would be, do we want to expose to the users that
> ChangeLogStateBackend is wrapping an inner state backend or not? If not,
> option 3 is the best. If we do, if we want to teach the users and help them
> build the understanding of how things are working underneath, option 5 or 6
> are better.
>
> Best,
> Piotrek
>
> śr., 2 cze 2021 o 04:36 Yun Tang  napisał(a):
>
> > Hi Yuan, thanks for launching this discussion.
> >
> > I prefer option-3 as this is the easiest to understand for users.
> >
> >
> > Best
> > Yun Tang
> > 
> > From: Roman Khachatryan 
> > Sent: Monday, May 31, 2021 16:53
> > To: dev 
> > Subject: Re: [DISCUSS][Statebackend][Runtime] Changelog Statebackend
> > Configuration Proposal
> >
> > Hey Yuan, thanks for the proposal
> >
> > I think Option 3 is the simplest to use and exposes less details than any
> > other.
> > It's also consistent with the current way of configuring state
> > backends, as long as we treat change logging as a common feature
> > applicable to any state backend, like e.g.
> > state.backend.local-recovery.
> >
> > Option 6 seems slightly less preferable as it exposes more details but
> > I think is the most viable alternative.
> >
> > Regards,
> > Roman
> >
> >
> > On Mon, May 31, 2021 at 8:39 AM Yuan Mei  wrote:
> > >
> > > Hey all,
> > >
> > > We would like to start a discussion on how to enable/config Changelog
> > > Statebakcend.
> > >
> > > As part of FLIP-158[1], Changelog state backend wraps on top of
> existing
> > > state backend (HashMapStateBackend, EmbeddedRocksDBStateBackend and may
> > > expect more) and delegates state changes to the underlying state
> > backends.
> > > This thread is to discuss the problem of how Changelog StateBackend
> > should
> > > be enabled and configured.
> > >
> > > Proposed options to enable/config state changelog is listed below:
> > >
> > > Option 1: Enable Changelog Statebackend through a Boolean Flag
> > >
> > > Option 2: Enable Changelog Statebackend through a Boolean Flag + a
> > Special
> > > Case
> > >
> > > Option 3: Enable Changelog Statebackend through a Boolean Flag + W/O
> > > ChangelogStateBackend Exposed
> > >
> > > Option 4: Explicit Nested Configuration + “changelog.inner” prefix for
> > > inner backend
> > >
> > > Option 5: Explicit Nested Configuration + inner state backend
> > configuration
> > > unchanged
> > >
> > > Option 6: Config Changelog and Inner Statebackend All-Together
> > >
> > > Details of each option can be found here:
> > >
> >
> https://docs.google.com/document/d/13AaCf5fczYTDHZ4G1mgYL685FqbnoEhgo0cdwuJlZmw/edit?usp=sharing
> > >
> > > When considering these options, please consider these four dimensions:
> > > 1 Consistency
> > > API/config should follow a consistent model and should not have
> > > contradicted logic beneath
> > > 2 Simplicity
> > > API should be easy to use and not introduce too much burden on users
> > > 3. Explicity
> > > API/config should not contain implicit assumptions and should be
> > intuitive
> > > to users
> > > 4. Extensibility
> > > With foreseen future, whether the current setting can be easily
> extended
> > >
> > > Please let us know what do you think and please keep the discussion in
> > this
> > > mailing thread.
> > >
> > > [1]
> > >
> >
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-158%3A+Generalized+incremental+checkpoints
> > >
> > > Best
> > > Yuan
> >
>

Re: Re: Re: [ANNOUNCE] New Apache Flink Committer - Rui Li

[Yu Li]

Congratulations Rui!

Best Regards,
Yu


On Fri, 23 Apr 2021 at 10:40, Guowei Ma  wrote:

> Congratulations, Rui!
> Best,
> Guowei
>
>
> On Fri, Apr 23, 2021 at 10:38 AM Yun Tang  wrote:
>
> > Congratulations, Rui!
> >
> > Best,
> > Yun Tang
> > 
> > From: Xuannan Su 
> > Sent: Friday, April 23, 2021 10:01
> > To: dev@flink.apache.org ; matth...@ververica.com
> <
> > matth...@ververica.com>
> > Subject: Re: Re: Re: [ANNOUNCE] New Apache Flink Committer - Rui Li
> >
> > Congratulations Rui!
> >
> > Best,
> > Xuannan
> > On Apr 22, 2021, 6:23 PM +0800, M Shengkai Fang ,
> > wrote:
> > >
> > > Congratulations Rui!
> >
>

Re: [VOTE] Apache Flink Stateful Functions 3.0.0, release candidate #1

[Yu Li]

+1 (binding)

Checked sums and signatures: OK
Checked RAT and end-to-end tests: OK
Checked version in pom/README/setup.py files: OK
Checked release notes: OK
Checked docker PR: OK

Thanks for driving this release, Gordon!

Best Regards,
Yu


On Fri, 2 Apr 2021 at 09:22, Seth Wiesman  wrote:

> +1 (non-binding)
>
> - Built from source and executed end to end tests
> - Checked licenses and signatures
> - Deployed remote Java SDK to gke cluster
> - Took savepoint and statefully rescaled
>
> Seth
>
> On Thu, Apr 1, 2021 at 9:05 AM Konstantin Knauf  wrote:
>
> > +1 (non-binding)
> >
> > - mvn clean install -Prun-e2e-tests (java 8) from source
> > - python3 -m unittest tests
> > - spin up Statefun Cluster on EKS with an image built from the
> Dockerfiles
> > of [1]
> > - run Python & Java Greeter example on AWS Lambda
> > - read through documentation (opened [2] to fix some tpoys)
> >
> > [1] https://github.com/apache/flink-statefun-docker/pull/13
> > [2] https://github.com/apache/flink-statefun/pull/219
> >
> > On Thu, Apr 1, 2021 at 6:46 AM Tzu-Li (Gordon) Tai 
> > wrote:
> >
> > > +1 (binding)
> > >
> > > - verified signatures and hashes
> > > - NOTICE and LICENSE files in statefun-flink-distribution,
> > > statefun-protobuf-shaded, and statefun-sdk-java looks sane
> > > - maven clean install -Prun-e2e-tests (java 8) from source
> > > - ran all examples and tutorials in apache/flink-statefun-playground
> with
> > > the new artifacts
> > > - Ran my SDK verifier utility [1] against the new Java and Python SDKs.
> > >
> > > Cheers,
> > > Gordon
> > >
> > > [1] https://github.com/tzulitai/statefun-sdk-verifier
> > >
> > > On Wed, Mar 31, 2021 at 8:50 PM Igal Shilman 
> wrote:
> > >
> > > > Thanks Gordon for managing the release!
> > > >
> > > > +1 (non binding) from my side:
> > > >
> > > > Here are the results of my testing:
> > > > - verified the signatures
> > > > - verified that the source distribution doesn't contain any binary
> > files
> > > > - ran mvn clean install -Prun-e2e-tests with java8
> > > > - ran the smoke test that sends 100 million messages locally.
> > > > - extended the smoke test to include the remote sdks (1 function in
> the
> > > > Java SDK, 1 function in the Python SDK), and it passes.
> > > > - deployed to kubernetes with minio as an S3 replacement.
> > > >
> > > >
> > > > On Tue, Mar 30, 2021 at 12:29 PM Tzu-Li (Gordon) Tai <
> > > tzuli...@apache.org>
> > > > wrote:
> > > >
> > > > > Hi everyone,
> > > > >
> > > > > Please review and vote on the release candidate #1 for the version
> > > 3.0.0
> > > > of
> > > > > Apache Flink Stateful Functions, as follows:
> > > > > [ ] +1, Approve the release
> > > > > [ ] -1, Do not approve the release (please provide specific
> comments)
> > > > >
> > > > > **Testing Guideline**
> > > > >
> > > > > You can find here [1] a page in the project wiki on instructions
> for
> > > > > testing.
> > > > > To cast a vote, it is not necessary to perform all listed checks,
> > > > > but please mention which checks you have performed when voting.
> > > > >
> > > > > **Release Overview**
> > > > >
> > > > > As an overview, the release consists of the following:
> > > > > a) Stateful Functions canonical source distribution, to be deployed
> > to
> > > > the
> > > > > release repository at dist.apache.org
> > > > > b) Stateful Functions Python SDK distributions to be deployed to
> PyPI
> > > > > c) Maven artifacts to be deployed to the Maven Central Repository
> > > > > d) New Dockerfiles for the release
> > > > >
> > > > > **Staging Areas to Review**
> > > > >
> > > > > The staging areas containing the above mentioned artifacts are as
> > > > follows,
> > > > > for your review:
> > > > > * All artifacts for a) and b) can be found in the corresponding dev
> > > > > repository at dist.apache.org [2]
> > > > > * All artifacts for c) can be found at the Apache Nexus Repository
> > [3]
> > > > >
> > > > > All artifacts are signed with the key
> > > > > 1C1E2394D3194E1944613488F320986D35C33D6A [4]
> > > > >
> > > > > Other links for your review:
> > > > > * JIRA release notes [5]
> > > > > * source code tag “release-3.0.0-rc1” [6]
> > > > > * PR for the new Dockerfiles [7]
> > > > >
> > > > > **Vote Duration**
> > > > >
> > > > > The voting time will run for at least 72 hours. I’m targeting this
> > vote
> > > > to
> > > > > last until April. 2nd, 12pm CET.
> > > > > It is adopted by majority approval, with at least 3 PMC affirmative
> > > > votes.
> > > > >
> > > > > Thanks,
> > > > > Gordon
> > > > >
> > > > > [1]
> > > > >
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/FLINK/Verifying+a+Flink+Stateful+Functions+Release
> > > > > [2]
> > > >
> https://dist.apache.org/repos/dist/dev/flink/flink-statefun-3.0.0-rc1/
> > > > > [3]
> > > > >
> > >
> https://repository.apache.org/content/repositories/orgapacheflink-1415/
> > > > > [4] https://dist.apache.org/repos/dist/release/flink/KEYS
> > > > > [5]
> > > > >
> > > > >
> > > >
> > >
> >
> 

Re: [VOTE] FLIP-151: Incremental snapshots for heap-based state backend

[Yu Li]

+1 (binding)

The latest FLIP document LGTM. Thanks for driving this Roman!

Best Regards,
Yu


On Thu, 4 Mar 2021 at 18:24, David Anderson  wrote:

> +1 (non-binding)
>
> On Mon, Mar 1, 2021 at 10:12 AM Roman Khachatryan 
> wrote:
>
> > Hi everyone,
> >
> > since the discussion [1] about FLIP-151 [2] seems to have reached a
> > consensus, I'd like to start a formal vote for the FLIP.
> >
> > Please vote +1 to approve the FLIP, or -1 with a comment. The vote will
> be
> > open at least until Wednesday, Mar 3rd.
> >
> > [1] https://s.apache.org/flip-151-discussion
> > [2]
> >
> >
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-151%3A+Incremental+snapshots+for+heap-based+state+backend
> >
> > Regards,
> > Roman
> >
>

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

[Yu Li]

+1 (binding)

- Checked the diff between 1.12.1 and 1.12.2-rc2: OK (
https://github.com/apache/flink/compare/release-1.12.1...release-1.12.2-rc2)
  - jackson version has been bumped to 2.10.5.1 through FLINK-21020 and all
NOTICE files updated correctly
  - beanutils version has been bumped to 1.9.4 through FLINK-21123 and all
NOTICE files updated correctly
  - testcontainer version has been bumped to 1.15.1 through FLINK-21277 and
no NOTICE files impact
  - japicmp version has been bumped to 1.12.1 and no NOTICE files impact
- Checked release notes: OK
- Checked sums and signatures: OK
- Maven clean install from source: OK
- Checked the jars in the staging repo: OK
- Checked the website updates: OK (minor: corrected fix version of
FLINK-21515  to make
sure the website PR consistent with release note)

Note: there's a vulnerability suspicion against 1.12.2-rc2 reported in
user-zh mailing list [1] w/o enough evidence/information. Have asked the
reporter to do more testing to confirm and I don't think it's a blocker for
the release, but just a note here in case anyone has a different opinion.

Thanks a lot for managing the new RC!

Best Regards,
Yu

[1] http://apache-flink.147419.n8.nabble.com/flink-1-12-2-rc2-td11023.html

On Tue, 2 Mar 2021 at 01:51, Piotr Nowojski  wrote:

> +1 (binding)
>
> For the RC2 I have additionally confirmed that "stop-with-savepoint", and
> "stop-with-savepoint --drain" seems to be working.
>
> Piotrek
>
> pon., 1 mar 2021 o 11:18 Matthias Pohl 
> napisał(a):
>
> > Thanks for managing release 1.12.2, Yuan & Roman.
> >
> > +1 (non-binding)
> >
> > - Verified checksums and GPG of artifacts in [1]
> > - Build the sources locally without errors
> > - Started a local standalone cluster and deployed WordCount without
> > problems (no suspicious logs identified)
> > - Verified FLINK-21030 [2] by running the example jobs from the
> > FLINK-21030-related SavepointITCase tests
> >
> > Best,
> > Matthias
> >
> > [1] https://dist.apache.org/repos/dist/dev/flink/flink-1.12.2-rc2/
> > [2] https://issues.apache.org/jira/browse/FLINK-21030
> >
> > On Sun, Feb 28, 2021 at 2:41 PM Yuan Mei  wrote:
> >
> > > Hey Roman,
> > >
> > > Thank you very much for preparing RC2.
> > >
> > > +1 from my side.
> > >
> > > 1. Verified Checksums and GPG signatures.
> > > 2. Verified that the source archives do not contain any binaries.
> > > 3. Successfully Built the source with Maven.
> > > 4. Started a local Flink cluster, ran the streaming WordCount example
> > with
> > > WebUI,
> > > checked the output and JM/TM log, no suspicious output/log.
> > > 5. Repeat Step 4 with the binary release as well, no suspicious
> > output/log.
> > > 6. Checked for source and binary release to make sure both an Apache
> > > License file and a NOTICE file are included.
> > > 7. Manually verified that no pom file changes between 1.12.2-rc1 and
> > > 1.12.2-rc2; no obvious license problem.
> > > 8. Review the release PR for RC2 updates, and double confirmed the
> > > change-list for 1.12.2.
> > >
> > > Best,
> > > Yuan
> > >
> > > On Sat, Feb 27, 2021 at 7:19 AM Roman Khachatryan 
> > > wrote:
> > >
> > > > Hi everyone,
> > > >
> > > > Please review and vote on the release candidate #1 for the version
> > > 1.12.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 0D545F264D2DFDEBFD4E038F97B4625E2FCF517C [3],
> > > > * all artifacts to be deployed to the Maven Central Repository [4],
> > > > * source code tag "release-1.12.2-rc2" [5],
> > > > * website pull request listing the new release and adding
> announcement
> > > blog
> > > > post [6].
> > > >
> > > > The vote will be open for at least 72 hours. It is adopted by
> majority
> > > > approval, with at least 3 PMC affirmative votes.
> > > >
> > > > [1]
> > > >
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12349502=12315522
> > > > [2] https://dist.apache.org/repos/dist/dev/flink/flink-1.12.2-rc2/
> > > > [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> > > > [4]
> > > >
> > https://repository.apache.org/content/repositories/orgapacheflink-1414/
> > > > [5] https://github.com/apache/flink/releases/tag/release-1.12.2-rc2
> > > > [6] https://github.com/apache/flink-web/pull/418
> > > >
> > > > Regards,
> > > > Roman
> > > >
> >
>

Re: [ANNOUNCE] New Apache Flink Committers - Wei Zhong and Xingbo Huang

[Yu Li]

Congratulations Wei and Xingbo!

Best Regards,
Yu


On Mon, 22 Feb 2021 at 15:56, Till Rohrmann  wrote:

> Congratulations Wei & Xingbo. Great to have you as committers in the
> community now.
>
> Cheers,
> Till
>
> On Mon, Feb 22, 2021 at 5:08 AM Xintong Song 
> wrote:
>
> > Congratulations, Wei & Xingbo~! Welcome aboard.
> >
> > Thank you~
> >
> > Xintong Song
> >
> >
> >
> > On Mon, Feb 22, 2021 at 11:48 AM Dian Fu  wrote:
> >
> > > Hi all,
> > >
> > > On behalf of the PMC, I’m very happy to announce that Wei Zhong and
> > Xingbo
> > > Huang have accepted the invitation to become Flink committers.
> > >
> > > - Wei Zhong mainly works on PyFlink and has driven several important
> > > features in PyFlink, e.g. Python UDF dependency management (FLIP-78),
> > > Python UDF support in SQL (FLIP-106, FLIP-114), Python UDAF support
> > > (FLIP-139), etc. He has contributed the first PR of PyFlink and have
> > > contributed 100+ commits since then.
> > >
> > > - Xingbo Huang's contribution is also mainly in PyFlink and has driven
> > > several important features in PyFlink, e.g. performance optimizing for
> > > Python UDF and Python UDAF (FLIP-121, FLINK-16747, FLINK-19236), Pandas
> > > UDAF support (FLIP-137), Python UDTF support (FLINK-14500), row-based
> > > Operations support in Python Table API (FLINK-20479), etc. He is also
> > > actively helping on answering questions in the user mailing list,
> helping
> > > on the release check, monitoring the status of the azure pipeline, etc.
> > >
> > > Please join me in congratulating Wei Zhong and Xingbo Huang for
> becoming
> > > Flink committers!
> > >
> > > Regards,
> > > Dian
> >
>

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

[Yu Li]

+1 (binding)

- Checked the diff between 1.12.1 and 1.12.2: OK (
https://github.com/apache/flink/compare/release-1.12.1...release-1.12.2-rc1)
  - jackson version has been bumped to 2.10.5.1 through FLINK-21020 and all
NOTICE files updated correctly
  - beanutils version has been bumped to 1.9.4 through FLINK-21123 and all
NOTICE files updated correctly
  - testcontainer version has been bumped to 1.15.1 through FLINK-21277 and
no NOTICE files impact
  - japicmp version has been bumped to 1.12.1 and no NOTICE files impact
- Checked release notes: OK
- Checked sums and signatures: OK
- Maven clean install from source: OK
- Checked the jars in the staging repo: OK
- Checked binary archive: OK
- Approved the website updates (left some notes in PR)

Thanks a lot for putting the RC together!

Best Regards,
Yu


On Sat, 20 Feb 2021 at 12:59, Xintong Song  wrote:

> +1 (non-binding)
>
> - verified checksums & signatures
> - reviewed website PR
> - build from source
> - run example jobs
>   - standalone session & yarn per-job
>   - jobs work as expected
>   - ui & logs look good
>
> Thank you~
>
> Xintong Song
>
>
>
> On Fri, Feb 19, 2021 at 9:59 PM Piotr Nowojski 
> wrote:
>
> > Hi,
> >
> > Thanks for preparing this release candidate.
> >
> > +1 from my side
> >
> > 1. I was monitoring recent builds for Unaligned Checkpoint issues and I
> can
> > confirm that it seems we don't have any failures in the last couple of
> > weeks.
> > 2. There are no tickets with fix version set to 1.12.2. There are two
> > blocker bugs for 1.12.3, but they are still quite far from being merged
> and
> > they shouldn't block the 1.12.2 release, as they have been present in the
> > past release already.
> > 3. I double confirmed that there are no dependency changes between 1.12.1
> > and 1.12.2-RC1, apart of the upgrade of `commons-beanutils` from 1.9.3 to
> > 1.9.4, which had and maintained Apache 2.0 license.
> >
> > Piotrek
> >
> > pt., 19 lut 2021 o 10:24 Yuan Mei  napisał(a):
> >
> > > Hey Roman,
> > >
> > > Thanks for preparing RC1!
> > >
> > > +1 from my side.
> > >
> > > 1. Run-through UnalignedCheckpointITCase for 800+ rounds to make
> > > sure UnalignedCheckpoint is stable
> > > 2. Verified Checksums and GPG Signature
> > > 3. Verified that the source archives do not contain any binaries
> > > 4. Successfully Built the source with Maven, started a local Flink
> > cluster,
> > > and ran the streaming WordCount example with WebMonitor without
> > suspicious
> > > output
> > > 5. Successfully ran the streaming WordCount example with the binary
> > release
> > > as well
> > > 6. Checked for source and binary release to make sure both an Apache
> > > License file and a NOTICE file are included
> > > 7. Manually check all pom file changes since the last release (Flink
> > > 1.12.1); no obvious license problem for me (Need someone to double
> > confirm
> > > this).
> > >
> > > Best
> > > Yuan
> > >
> > > On Wed, Feb 17, 2021 at 3:25 AM Roman Khachatryan 
> > > wrote:
> > >
> > > > Hi everyone,
> > > > Please review and vote on the release candidate #1 for the version
> > > 1.12.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 0D545F264D2DFDEBFD4E038F97B4625E2FCF517C [3],
> > > > * all artifacts to be deployed to the Maven Central Repository [4],
> > > > * source code tag "release-1.12.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.
> > > >
> > > >
> > > > Regards,
> > > > Roman
> > > >
> > > > [1]
> > > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12349502=12315522
> > > > [2] https://dist.apache.org/repos/dist/dev/flink/flink-1.12.2-rc1/
> > > > [3] https://dist.apache.org/repos/dist/release/flink/KEYS
> > > > [4]
> > > >
> > https://repository.apache.org/content/repositories/orgapacheflink-1413/
> > > > [5] https://github.com/apache/flink/releases/tag/release-1.12.2-rc1
> > > > [6] https://github.com/apache/flink-web/pull/418
> > > >
> > >
> >
>

Re: [ANNOUNCE] Welcome Roman Khachatryan a new Apache Flink Committer

[Yu Li]

Congratulations, Roman!

Best Regards,
Yu


On Thu, 18 Feb 2021 at 11:05, Xingbo Huang  wrote:

> Congratulations Roman!
>
> Best,
> Xingbo
>
> Yang Wang  于2021年2月18日周四 上午10:29写道：
>
> > Congrats Roman!
> >
> > Best,
> > Yang
> >
> > Xintong Song  于2021年2月18日周四 上午10:00写道：
> >
> > > Congratulations, Roman~!
> > >
> > > Thank you~
> > >
> > > Xintong Song
> > >
> > >
> > >
> > > On Thu, Feb 18, 2021 at 9:42 AM Dian Fu  wrote:
> > >
> > > > Congratulations, Roman!
> > > >
> > > > Regards,
> > > > Dian
> > > >
> > > > > 在 2021年2月16日，下午5:56，Yuan Mei  写道：
> > > > >
> > > > > Well deserved! Congrats Roman!
> > > > >
> > > > > Best,
> > > > > Yuan
> > > > >
> > > > > On Tue, Feb 16, 2021 at 5:10 PM Guowei Ma 
> > > wrote:
> > > > >
> > > > >> Congratulations Roman!
> > > > >> Best,
> > > > >> Guowei
> > > > >>
> > > > >>
> > > > >> On Thu, Feb 11, 2021 at 3:37 PM Yun Tang 
> wrote:
> > > > >>
> > > > >>> Congratulations, Roman!
> > > > >>>
> > > > >>> Today is also the beginning of Chinese Spring Festival holiday,
> at
> > > > which
> > > > >>> we Chinese celebrate across the world for the next lunar new
> year,
> > > and
> > > > >> also
> > > > >>> very happy to have you on board!
> > > > >>>
> > > > >>> Best
> > > > >>> Yun Tang
> > > > >>> 
> > > > >>> From: Roman Khachatryan 
> > > > >>> Sent: Thursday, February 11, 2021 4:03
> > > > >>> To: matth...@ververica.com 
> > > > >>> Cc: dev 
> > > > >>> Subject: Re: [ANNOUNCE] Welcome Roman Khachatryan a new Apache
> > Flink
> > > > >>> Committer
> > > > >>>
> > > > >>> Many thanks to all of you!
> > > > >>>
> > > > >>> Regards,
> > > > >>> Roman
> > > > >>>
> > > > >>>
> > > > >>> On Wed, Feb 10, 2021 at 7:12 PM Matthias Pohl <
> > > matth...@ververica.com>
> > > > >>> wrote:
> > > > >>>
> > > >  Congratulations, Roman! :-)
> > > > 
> > > >  On Wed, Feb 10, 2021 at 3:23 PM Kezhu Wang 
> > > wrote:
> > > > 
> > > > > Congratulations!
> > > > >
> > > > > Best,
> > > > > Kezhu Wang
> > > > >
> > > > >
> > > > > On February 10, 2021 at 21:53:52, Dawid Wysakowicz (
> > > > > dwysakow...@apache.org)
> > > > > wrote:
> > > > >
> > > > > Congratulations Roman! Glad to have you on board!
> > > > >
> > > > > Best,
> > > > >
> > > > > Dawid
> > > > >
> > > > > On 10/02/2021 14:44, Igal Shilman wrote:
> > > > >> Welcome Roman!
> > > > >> Top-notch stuff! :)
> > > > >>
> > > > >> All the best,
> > > > >> Igal.
> > > > >>
> > > > >> On Wed, Feb 10, 2021 at 2:15 PM Kostas Kloudas <
> > > kklou...@gmail.com>
> > > > > wrote:
> > > > >>
> > > > >>> Congrats Roman!
> > > > >>>
> > > > >>> Kostas
> > > > >>>
> > > > >>> On Wed, Feb 10, 2021 at 2:08 PM Arvid Heise <
> ar...@apache.org>
> > > > >>> wrote:
> > > >  Congrats! Well deserved.
> > > > 
> > > >  On Wed, Feb 10, 2021 at 1:54 PM Yun Gao
> > > > >>>  > > > >>
> > > >  wrote:
> > > > 
> > > > > Congratulations Roman!
> > > > >
> > > > > Best,
> > > > > Yun
> > > > >
> > > > >
> > > > > --Original Mail --
> > > > > Sender:Till Rohrmann 
> > > > > Send Date:Wed Feb 10 20:53:21 2021
> > > > > Recipients:dev 
> > > > > CC:Khachatryan Roman , Roman
> > > > > Khachatryan
> > > > >>> <
> > > > > ro...@apache.org>
> > > > > Subject:Re: [ANNOUNCE] Welcome Roman Khachatryan a new
> Apache
> > > > >> Flink
> > > > > Committer
> > > > > Congratulations Roman :-)
> > > > >
> > > > > Cheers,
> > > > > Till
> > > > >
> > > > > On Wed, Feb 10, 2021 at 1:01 PM Konstantin Knauf <
> > > > >>> kna...@apache.org>
> > > > > wrote:
> > > > >
> > > > >> Congratulations Roman!
> > > > >>
> > > > >> On Wed, Feb 10, 2021 at 11:29 AM Piotr Nowojski <
> > > > >>> pnowoj...@apache.org>
> > > > >> wrote:
> > > > >>
> > > > >>> Hi everyone,
> > > > >>>
> > > > >>> I'm very happy to announce that Roman Khachatryan has
> > > accepted
> > > > >>> the
> > > > >>> invitation to
> > > > >>> become a Flink committer.
> > > > >>>
> > > > >>> Roman has been recently active in the runtime parts of
> the
> > > > >> Flink.
> > > > >>> He is
> > > > >> one
> > > > >>> of the main developers behind FLIP-76 Unaligned
> > Checkpoints,
> > > > >>> FLIP-151
> > > > >>> Incremental Heap/FS State Backend [3] and providing a
> > faster
> > > > >> checkpointing
> > > > >>> mechanism in FLIP-158.
> > > > >>>
> > > > >>> Please join me in congratulating Roman for becoming a
> Flink
> > > > >>> committer!
> > > > >>> Best,
> > > > >>> Piotrek
> > > > >>>
> > > > 

Re: [DISCUSS] Releasing Apache Flink 1.12.2

[Yu Li]

+1 for releasing 1.12.2, and thanks for volunteering to be our release
manager Yuan.

Besides the mentioned issues, I could see two more blockers with 1.12.2 as
fix version [1] and need some tracking:
* FLINK-21013  Blink
planner does not ingest timestamp into StreamRecord
* FLINK- 21030  Broken
job restart for job with disjoint graph

Best Regards,
Yu

[1] https://s.apache.org/flink-1.12.2-blockers


On Sat, 6 Feb 2021 at 08:57, Kurt Young  wrote:

> Thanks for being our release manager Yuan.
>
> We found a out of memory issue [1] which will affect most batch jobs thus I
> think
> it would be great if we can include this fix in 1.12.2.
>
> [1] https://issues.apache.org/jira/browse/FLINK-20663
>
> Best,
> Kurt
>
>
> On Sat, Feb 6, 2021 at 12:36 AM Till Rohrmann 
> wrote:
>
> > Thanks for volunteering for being our release manager Yuan :-)
> >
> > +1 for a timely bug fix release.
> >
> > I will try to review the PR for FLINK- 20417 [1] which is a good fix to
> > include in the next bug fix release. We don't have to block the release
> on
> > this fix though.
> >
> > [1] https://issues.apache.org/jira/browse/FLINK-20417
> >
> > Cheers,
> > Till
> >
> > On Fri, Feb 5, 2021 at 5:12 PM Piotr Nowojski 
> > wrote:
> >
> > > Hi,
> > >
> > > Thanks Yuan for bringing up this topic.
> > >
> > > +1 for the quick 1.12.2 release.
> > >
> > > As Yuan mentioned, me and Roman can help whenever committer rights will
> > be
> > > required.
> > >
> > > > I am a Firefox user and I just fixed a long lasting bug
> > > https://github.com/apache/flink/pull/14848 , wish this would be merged
> > in
> > > this release.
> > >
> > > I will push to speed up review of your PR. Let's try to merge it before
> > > 1.12.2, but at the same time I wouldn't block the release on this bug.
> > >
> > > Best,
> > > Piotrek
> > >
> > > pt., 5 lut 2021 o 12:12 郁蓝  napisał(a):
> > >
> > > > Hi Yuan,
> > > >
> > > >
> > > > I am a Firefox user and I just fixed a long lasting bug
> > > > https://github.com/apache/flink/pull/14848 , wish this would be
> merged
> > > in
> > > > this release.
> > > >
> > > >
> > > > Best wishes
> > > >
> > > >
> > > >
> > > > --原始邮件--
> > > > 发件人:
> > > >   "dev"
> > > > <
> > > > yuanmei.w...@gmail.com;
> > > > 发送时间:2021年2月5日(星期五) 晚上6:36
> > > > 收件人:"dev" > > >
> > > > 主题:[DISCUSS] Releasing Apache Flink 1.12.2
> > > >
> > > >
> > > >
> > > > Hey devs,
> > > >
> > > > One of the major issues that have not been resolved in Apache Flink
> > > 1.12.1
> > > > is "unaligned
> > > > checkpoint recovery may lead to corrupted data stream"[1]. Since the
> > > > problem is now fixed and
> > > > it is critical to the users, I would like to kick off a discussion on
> > > > releasing Flink 1.12.2 that
> > > > includes unaligned checkpoint fixes.
> > > >
> > > > I would like to volunteer myself for managing this release. But I
> > noticed
> > > > that some of the release
> > > > steps may require committer authorities. Luckily, Piotr and Roman are
> > > very
> > > > kind to provide help
> > > > on such steps.
> > > >
> > > > Apart from the unaligned checkpoint issue, please let us know in this
> > > > thread if there are any
> > > > other fixes that we should try to include in this version. I'll try
> to
> > > > communicate with the issue
> > > > owners and come up with a time estimation next week.
> > > >
> > > > [1] https://issues.apache.org/jira/browse/FLINK-20654
> > > >
> > > > Best
> > > > Yuan
> > >
> >
>

Re: [VOTE] FLIP-160: Declarative scheduler

[Yu Li]

+1 (binding)

Best Regards,
Yu


On Mon, 1 Feb 2021 at 17:21, Matthias Pohl  wrote:

> +1 (non-binding)
>
> Thanks,
> Matthias
>
> On Mon, Feb 1, 2021 at 4:22 AM Zhu Zhu  wrote:
>
> > +1 (binding)
> >
> > Thanks,
> > Zhu
> >
> > Yang Wang  于2021年2月1日周一 上午11:04写道：
> >
> > > +1 (non-binding)
> > >
> > > Best,
> > > Yang
> > >
> > > Yangze Guo  于2021年2月1日周一 上午9:50写道：
> > >
> > > > +1 (non-binding)
> > > >
> > > > Best,
> > > > Yangze Guo
> > > >
> > > > On Sat, Jan 30, 2021 at 8:40 AM Xintong Song 
> > > > wrote:
> > > > >
> > > > > +1 (binding)
> > > > >
> > > > > Thank you~
> > > > >
> > > > > Xintong Song
> > > > >
> > > > >
> > > > >
> > > > > On Fri, Jan 29, 2021 at 10:41 PM Robert Metzger <
> rmetz...@apache.org
> > >
> > > > wrote:
> > > > >
> > > > > > ... and thanks a lot for your work :) I'm really excited about
> > > finally
> > > > > > adding this feature to Flink!
> > > > > >
> > > > > >
> > > > > > On Fri, Jan 29, 2021 at 3:40 PM Robert Metzger <
> > rmetz...@apache.org>
> > > > > > wrote:
> > > > > >
> > > > > > > +1 (binding)
> > > > > > >
> > > > > > > On Fri, Jan 29, 2021 at 3:23 PM Till Rohrmann <
> > > trohrm...@apache.org>
> > > > > > > wrote:
> > > > > > >
> > > > > > >> Hi all,
> > > > > > >>
> > > > > > >> since the discussion [1] about FLIP-160 [2] seems to have
> > reached
> > > a
> > > > > > >> consensus, I'd like to start a formal vote for the FLIP.
> > > > > > >>
> > > > > > >> Please vote +1 to approve the FLIP, or -1 with a comment. The
> > vote
> > > > will
> > > > > > be
> > > > > > >> open at least until Wednesday, Feb 3rd.
> > > > > > >>
> > > > > > >> Cheers,
> > > > > > >> Till
> > > > > > >>
> > > > > > >> [1]
> > > > > > >>
> > > > > > >>
> > > > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/r604a01f739639e2a5f093fbe7894c172125530332747ecf6990a6ce4%40%3Cdev.flink.apache.org%3E
> > > > > > >> [2]
> > > > > > >>
> > > > > > >>
> > > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-160%3A+Declarative+Scheduler
> > > > > > >>
> > > > > > >
> > > > > >
> > > >
> > >
>

Re: [VOTE] FLIP-159: Reactive Mode

[Yu Li]

+1 (binding)

Thanks for the efforts Robert!

Best Regards,
Yu


On Mon, 1 Feb 2021 at 17:19, Matthias Pohl  wrote:

> Thanks Robert and congratulations on your first FLIP.
> +1 (non-binding)
>
> Matthias
>
> On Mon, Feb 1, 2021 at 4:22 AM Zhu Zhu  wrote:
>
> > +1 (binding)
> >
> > Thanks,
> > Zhu
> >
> > Till Rohrmann  于2021年1月29日周五 下午10:23写道：
> >
> > > LGTM. Thanks for the work Robert!
> > >
> > > +1 (binding)
> > >
> > > Cheers,
> > > Till
> > >
> > > On Thu, Jan 28, 2021 at 11:27 AM Yang Wang 
> > wrote:
> > >
> > > > Thanks Robert for your great work on this FLIP. This is really a big
> > step
> > > > to make Flink auto scalable.
> > > >
> > > > +1 (non-binding)
> > > >
> > > >
> > > > Best,
> > > > Yang
> > > >
> > > > Robert Metzger  于2021年1月28日周四 下午4:32写道：
> > > >
> > > > > @Yangze: That's something I overlooked. I should have waited. If
> > > FLIP-160
> > > > > is rejected or undergoes fundamental changes, I'll cancel this vote
> > and
> > > > > rewrite FLIP-159.
> > > > > But I have the impression that there were no major concerns
> regarding
> > > > > FLIP-160 so far.
> > > > >
> > > > > On Thu, Jan 28, 2021 at 8:46 AM Yangze Guo 
> > wrote:
> > > > >
> > > > > > Thanks for driving this, Robert! LGTM.
> > > > > >
> > > > > > +1
> > > > > >
> > > > > > minor: Just a little confused about the program. It seems this
> > > > > > proposal relies on the FLIP-160, which is still under discussion.
> > > > > > Should we always vote for the prerequisite first?
> > > > > >
> > > > > > Best,
> > > > > > Yangze Guo
> > > > > >
> > > > > >
> > > > > > On Thu, Jan 28, 2021 at 3:27 PM Xintong Song <
> > tonysong...@gmail.com>
> > > > > > wrote:
> > > > > > >
> > > > > > > Thanks Robert. LGTM.
> > > > > > >
> > > > > > > +1 (binding)
> > > > > > >
> > > > > > > Thank you~
> > > > > > >
> > > > > > > Xintong Song
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On Thu, Jan 28, 2021 at 2:50 PM Robert Metzger <
> > > rmetz...@apache.org>
> > > > > > wrote:
> > > > > > >
> > > > > > > > Hi all,
> > > > > > > >
> > > > > > > > since the discussion [1] about FLIP-159 [2] seems to have
> > > reached a
> > > > > > > > consensus, I'd like to start a formal vote for the FLIP.
> > > > > > > >
> > > > > > > > Please vote +1 to approve the FLIP, or -1 with a comment. The
> > > vote
> > > > > > will be
> > > > > > > > open at least until Tuesday, Feb 2nd.
> > > > > > > >
> > > > > > > > Best,
> > > > > > > > Robert
> > > > > > > >
> > > > > > > > [1]
> > > > > > > >
> > > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://lists.apache.org/thread.html/ra688faf9dca036500f0445c55671e70ba96c70f942afe650e9db8374%40%3Cdev.flink.apache.org%3E
> > > > > > > > [2]
> > > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-159%3A+Reactive+Mode
> > > > > > > >
> > > > > >
> > > > >
> > > >
> > >
>

Re: [ANNOUNCE] Apache Flink 1.10.3 released

[Yu Li]

Thanks Xintong for being our release manager and everyone else who made the
release possible!

Best Regards,
Yu


On Fri, 29 Jan 2021 at 15:05, Xintong Song  wrote:

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

Re: [ANNOUNCE] Welcome Guowei Ma as a new Apache Flink Committer

[Yu Li]

Congratulations and welcome, Guowei!

Best Regards,
Yu


On Wed, 20 Jan 2021 at 13:46, Xintong Song  wrote:

> Congratulations, Guowei~!
>
>
> Thank you~
>
> Xintong Song
>
>
>
> On Wed, Jan 20, 2021 at 1:42 PM Yuan Mei  wrote:
>
> > Congrats Guowei :-)
> >
> > Best,
> > Yuan
> >
> > On Wed, Jan 20, 2021 at 1:36 PM tison  wrote:
> >
> > > Congrats Guowei!
> > >
> > > Best,
> > > tison.
> > >
> > >
> > > Kurt Young  于2021年1月20日周三 下午1:34写道：
> > >
> > > > Hi everyone,
> > > >
> > > > I'm very happy to announce that Guowei Ma has accepted the invitation
> > to
> > > > become a Flink committer.
> > > >
> > > > Guowei is a very long term Flink developer, he has been extremely
> > helpful
> > > > with
> > > > some important runtime changes, and also been  active with answering
> > user
> > > > questions as well as discussing designs.
> > > >
> > > > Please join me in congratulating Guowei for becoming a Flink
> committer!
> > > >
> > > > Best,
> > > > Kurt
> > > >
> > >
> >
>

Re: [DISCUSS] Releasing Apache Flink 1.10.3

[Yu Li]

+1 for having a bugfix release for the 1.10 branch to fix the security
issue.

Thanks for driving the discussion Matthias!

Minor: CVE-2020-17519 is introduced by 1.11.0 [1] so we don't need to fix
it in 1.10.3, but CVE-2020-17518 [2] is needed.

Best Regards,
Yu

[1] https://s.apache.org/CVE-2020-17519
[2] https://s.apache.org/CVE-2020-17518


On Wed, 13 Jan 2021 at 16:57, Till Rohrmann  wrote:

> Thanks for starting this discussion Matthias. I agree with all of you that
> a final 1.10.3 release could be really helpful for our users. Given that CI
> passes, it shouldn't be too much overhead either.
>
> Cheers,
> Till
>
> On Wed, Jan 13, 2021 at 9:45 AM Xingbo Huang  wrote:
>
> > Thanks for starting this discussion, Matthias.
> >
> > +1 for releasing 1.10.3 as it contains a number of important fixes.
> >
> > Best,
> > Xingbo
> >
> > Xintong Song  于2021年1月13日周三 下午3:46写道：
> >
> > > Thanks for bringing this up, Matthias.
> > >
> > > Per the "Update Policy for old releases" [1], normally we do not
> release
> > > 1.10.x after 1.12.0 is released. However, the policy also says that we
> > are
> > > "open to discussing bugfix releases for even older versions".
> > >
> > > In this case, I'm +1 for releasing 1.10.3, for the dozens of
> > non-released
> > > fixes and the security flaws.
> > >
> > > As a reminder, I'd like to bring up FLINK-20906 [2] to be backported if
> > we
> > > are releasing 1.10.3, which updates the copyright year in NOTICE files
> to
> > > 2021.
> > >
> > > Thank you~
> > >
> > > Xintong Song
> > >
> > >
> > > [1] https://flink.apache.org/downloads.html
> > > [2] https://issues.apache.org/jira/browse/FLINK-20906
> > >
> > > On Tue, Jan 12, 2021 at 7:15 PM Matthias Pohl 
> > > wrote:
> > >
> > > > Hi,
> > > > I'd like to initiate a discussion on releasing Flink 1.10.3. There
> > were a
> > > > few requests in favor of this already in [1] and [2].
> > > >
> > > > I checked the release-1.10 branch: 55 commits are not released, yet.
> > > > Some non-released fixes that might be relevant are:
> > > > - FLINK-20218 [3] - fix "module 'urllib' has no attribute 'parse'"
> due
> > to
> > > > ProtoBuf version update
> > > > - FLINK-20013 [4] - BoundedBlockingSubpartition may leak network
> buffer
> > > > - FLINK-19252 [5] - temporary folder is not created when missing
> > > > - FLINK-19557 [6] - LeaderRetrievalListener notification upon
> ZooKeeper
> > > > reconnection
> > > > - FLINK-19523 [7] - hide sensitive information in logs
> > > >
> > > > In addition to that, we would like to include a backport for
> > > CVE-2020-17518
> > > > and CVE-2020-17519 to cover the request in [2].
> > > >
> > > > The travis-ci build chain for release-1.10 seems to be stable [8].
> > > > Any thoughts on that? Unfortunately, I cannot volunteer as a release
> > > > manager due to the lack of permissions. But I wanted to start the
> > > > discussion, anyway.
> > > >
> > > > Best,
> > > > Matthias
> > > >
> > > > [1]
> > > >
> > > >
> > >
> >
> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/ANNOUNCE-Weekly-Community-Update-2020-44-45-td46486.html#a47610
> > > > [2] https://issues.apache.org/jira/browse/FLINK-20875
> > > > [3] https://issues.apache.org/jira/browse/FLINK-20218
> > > > [4] https://issues.apache.org/jira/browse/FLINK-20013
> > > > [5] https://issues.apache.org/jira/browse/FLINK-19252
> > > > [6] https://issues.apache.org/jira/browse/FLINK-19557
> > > > [7] https://issues.apache.org/jira/browse/FLINK-19523
> > > > [8] https://travis-ci.com/github/apache/flink/builds/212749910
> > > >
> > >
> >
>

Re: [ANNOUNCE] Welcome Danny Cranmer as a new Apache Flink Committer

[Yu Li]

Congrats and welcome, Danny!

Best Regards,
Yu


On Wed, 13 Jan 2021 at 15:37, Yun Gao  wrote:

> Congratulations, Danny!
>
> Best,
>  Yun
>
>
> --
> From:Xintong Song 
> Send Time:2021 Jan. 13 (Wed.) 15:29
> To:dev 
> Subject:Re: [ANNOUNCE] Welcome Danny Cranmer as a new Apache Flink
> Committer
>
> Congratulations, Danny.
> Welcome aboard.
>
> Thank you~
>
> Xintong Song
>
>
>
> On Wed, Jan 13, 2021 at 3:25 PM Yun Tang  wrote:
>
> > Congratulations Danny!
> >
> > Best
> > Yun Tang
> > 
> > From: Jingsong Li 
> > Sent: Wednesday, January 13, 2021 14:23
> > To: dev 
> > Subject: Re: [ANNOUNCE] Welcome Danny Cranmer as a new Apache Flink
> > Committer
> >
> > Congrats, Danny!
> >
> > Best,
> > Jingsong
> >
> > On Tue, Jan 12, 2021 at 7:55 PM Leonard Xu  wrote:
> >
> > > Congratulations Danny!
> > >
> > > Best,
> > > Leonard
> > > > 在 2021年1月12日，19:44，Wei Zhong  写道：
> > > >
> > > > Congratulations Danny!
> > > >
> > > > Best,
> > > > Wei
> > > >
> > > >> 在 2021年1月12日，19:09，hailongwang <18868816...@163.com> 写道：
> > > >>
> > > >> Congratulations Danny!
> > > >>
> > > >> Best,
> > > >> Hailong在 2021-01-12 17:05:31，"Jark Wu"  写道：
> > > >>> Congratulations Danny!
> > > >>>
> > > >>> Best,
> > > >>> Jark
> > > >>>
> > > >>> On Tue, 12 Jan 2021 at 17:59, Yangze Guo 
> wrote:
> > > >>>
> > >  Congrats, Danny!
> > > 
> > >  Best,
> > >  Yangze Guo
> > > 
> > >  On Tue, Jan 12, 2021 at 5:55 PM Xingbo Huang 
> > > wrote:
> > > >
> > > > Congratulations, Danny!
> > > >
> > > > Best,
> > > > Xingbo
> > > >
> > > > Dian Fu  于2021年1月12日周二 下午5:48写道：
> > > >
> > > >> Congratulations, Danny!
> > > >>
> > > >> Regards,
> > > >> Dian
> > > >>
> > > >>> 在 2021年1月12日，下午5:40，Till Rohrmann  写道：
> > > >>>
> > > >>> Congrats and welcome Danny!
> > > >>>
> > > >>> Cheers,
> > > >>> Till
> > > >>>
> > > >>> On Tue, Jan 12, 2021 at 10:09 AM Dawid Wysakowicz <
> > > >> dwysakow...@apache.org>
> > > >>> wrote:
> > > >>>
> > >  Congratulations, Danny!
> > > 
> > >  Best,
> > > 
> > >  Dawid
> > > 
> > >  On 12/01/2021 09:52, Paul Lam wrote:
> > > > Congrats, Danny!
> > > >
> > > > Best,
> > > > Paul Lam
> > > >
> > > >> 2021年1月12日 16:48，Tzu-Li (Gordon) Tai 
> > 写道：
> > > >>
> > > >> Hi everyone,
> > > >>
> > > >> I'm very happy to announce that the Flink PMC has accepted
> > Danny
> > >  Cranmer to
> > > >> become a committer of the project.
> > > >>
> > > >> Danny has been extremely helpful on the mailing lists with
> > >  answering
> > >  user
> > > >> questions on the AWS Kinesis connector, and has driven
> > numerous
> > >  new
> > > >> features and timely bug fixes for the connector as well.
> > > >>
> > > >> Please join me in welcoming Danny :)
> > > >>
> > > >> Cheers,
> > > >> Gordon
> > > >
> > > 
> > > 
> > > >>
> > > >>
> > > 
> > > >
> > >
> > >
> >
> > --
> > Best, Jingsong Lee
> >
>

Re: [VOTE] FLIP-153: Support state access in Python DataStream API

[Yu Li]

+1 (binding)

Thanks for driving the FLIP!

Best Regards,
Yu


On Mon, 11 Jan 2021 at 14:30, Becket Qin  wrote:

> +1 (binding)
>
> Thanks for driving the FLIP, Shuiqiang.
>
> Jiangjie (Becket) Qin
>
> On Wed, Jan 6, 2021 at 2:58 PM Yun Tang  wrote:
>
> > +1 (binding)
> >
> > Best
> > Yun Tang
> > 
> > From: Wei Zhong 
> > Sent: Wednesday, January 6, 2021 14:07
> > To: dev 
> > Subject: Re: [VOTE] FLIP-153: Support state access in Python DataStream
> API
> >
> > +1 (non-binding)
> >
> > Best,
> > Wei
> >
> > > 在 2021年1月6日，14:05，Xingbo Huang  写道：
> > >
> > > +1 (non-binding)
> > >
> > > Best,
> > > Xingbo
> > >
> > > Dian Fu  于2021年1月6日周三 下午1:38写道：
> > >
> > >> +1 (binding)
> > >>
> > >>> 在 2021年1月6日，下午1:12，Shuiqiang Chen  写道：
> > >>>
> > >>> Hi devs,
> > >>>
> > >>> The discussion of the FLIP-153 [1] seems has reached a consensus
> > through
> > >>> the mailing thread [2]. I would like to start a vote for it.
> > >>>
> > >>> The vote will be opened until 11th January (72h), unless there is an
> > >>> objection or no enough votes.
> > >>>
> > >>> Best,
> > >>> Shuiqiang
> > >>>
> > >>> [1]:
> > >>>
> > >>
> >
> https://cwiki.apache.org/confluence/display/FLINK/FLIP-153%3A+Support+state+access+in+Python+DataStream+API
> > >>>
> > >>> [2]:
> > >>>
> > >>
> >
> http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-FLIP-153-Support-state-access-in-Python-DataStream-API-td47127.html
> > >>
> > >>
> >
> >
>

Re: [DISCUSS] FLIP-153: Support state access in Python DataStream API

[Yu Li]

Thanks for driving the discussion Shuiqiang, and sorry for chiming in late.

*bq. However, all the state access will be synchronized in the Java
operator and so there will be no concurrent access to the state backend.*
Could you add a section to explicitly mention this in the FLIP document? I
think single-threaded state access is an important prerequisite and it's
important for later contributors to know about this clearly, from both the
design doc and source codes.

The other parts LGTM, added some minor inline comments in the FLIP, please
take a look.

Thanks.

Best Regards,
Yu


On Fri, 18 Dec 2020 at 15:10, Shuiqiang Chen  wrote:

> Hi wei,
>
> Big thanks for pointing out the mistakes! I have updated the FLIP
> according to your suggestions.
>
> Best,
> Shuiqiang
>
> > 在 2020年12月18日，下午2:37，Wei Zhong  写道：
> >
> > Hi Shuiqiang,
> >
> > Thanks for driving this. +1 for this feature, just a minor comment to
> the design doc.
> >
> > The interface of the `AppendingState` should be:
> >
> > class AppendingState(State, Generic[IN, OUT]):
> >
> >   @abstractmethod
> >   def get(self) -> OUT:
> >   pass
> >
> >   @abstractmethod
> >   def add(self, value: IN) -> None:
> >   pass
> >
> > The output type and the input type of the `AppendingState` maybe
> different. And the definition of the child classes should be:
> >
> > class MergingState(AppendingState[IN, OUT]):
> >pass
> >
> >
> > class ListState(MergingState[T, Iterable[T]]):
> >
> >   @abstractmethod
> >   def update(self, values: List[T]) -> None:
> >   pass
> >
> >   @abstractmethod
> >   def add_all(self, values: List[T]) -> None:
> >   pass
> >
> >   def __iter__(self) -> Iterator[T]:
> >   return iter(self.get())
> >
> > Best,
> > Wei
> >
> >> 在 2020年12月17日，21:06，Shuiqiang Chen  写道：
> >>
> >> Hi Yun,
> >>
> >> Highly appreciate for your questions! I have the corresponding answers
> as bellow:
> >>
> >> Re 1: You are right that the state access occurs in an async thread.
> However, all the state access will be synchrouzed in the Java operator and
> so there will be no concurrent access to the state backend.
> >>
> >> Re 2: I think it could be handled well in Python DataStream API. In
> this case, there will be two operators and so also two keyed state backend.
> >>
> >> Re 3: Sure, you are right. We will store the current key which may be
> used by the timer.
> >>
> >> Re 4: Good point. State migration is still not covered in the current
> FLIP. I'd like to cover it in a separate FLIP as it should be orthogonal to
> this FLIP. I have updated the FLIP and added clear description for this.
> >>
> >> Re 5: Good point. We may need to introduce a Python querable state
> client if we want to support Queryable state for Python operators. I'd like
> to cover it in a separate FLIP. I have updated the FLIP and add it as a
> future work.
> >>
> >> Best,
> >> Shuiqiang
> >>
> >>> 在 2020年12月17日，下午12:08，Yun Tang  写道：
> >>>
> >>> Hi Shuiqiang,
> >>>
> >>> Thanks for driving this. I have several questions below:
> >>>
> >>>
> >>> 1.  Thread safety of state write-access. As you might know, state
> access is not thread-safe [1] in Flink, we depend on task single thread
> access. Since you change the state access to another async thread, can we
> still ensure this? It also includes not allow user to access state in its
> java operator along with the bundled python operator.
> >>> 2.  Number of keyed state backend per task. Flink would only have one
> keyed state-backend per operator and would only have one keyed state
> backend per operator chain (in the head operator if possible). However,
> once we use experimental features such as reinterpretAsKeyedStream [2], we
> could have two keyed state-backend in one operator chain within one task.
> Can python datastream API could handle this well?
> >>> 3.  Time to set current key. As we still need current key when
> registering timer [3], we need some place to hole the current key even not
> registered in keyed state backend.
> >>> 4.  State migration. Flink supports to migrate state automatically if
> new provided serializer is compatible with old serializer[4]. I'm afraid if
> python data stream API wraps user's serializer as
> BytePrimitiveArraySerializer, we will lose such functionality. Moreover,
> RocksDB will migrate state automatically on java side [5] and this will
> break if python related bytes involved.
> >>> 5.  Queryable state client. Currently, we only have java-based
> queryable state client [6], and we need another python-based queryable
> state client if involved python bytes.
> >>>
> >>> [1] https://issues.apache.org/jira/browse/FLINK-13072
> >>> [2]
> https://ci.apache.org/projects/flink/flink-docs-stable/dev/stream/experimental.html#reinterpreting-a-pre-partitioned-data-stream-as-keyed-stream
> >>> [3]
> 

Re: [VOTE] Apache Flink Stateful Functions 2.2.2, release candidate #2

[Yu Li]

+1 (binding)

Checked sums and signatures: OK
Checked no binaries in source distribution: OK
Checked RAT and end-to-end tests (8u101, 11.0.4): OK
Checked version in pom/README/setup.py files: OK
Checked website PR: OK

Thanks for driving this release, Gordon!

Best Regards,
Yu


On Fri, 25 Dec 2020 at 16:28, Dian Fu  wrote:

> Thanks a lot for driving this, Gordon!
>
> +1 (binding)
>
> - verified the checksum and signature
> - looked through the changes since 2.2.1 for license changes, verified the
> NOTICE file of statefun-flink-datastream and it looks good to me
> - the website PR LGTM
>
> Regards,
> Dian
>
> > 在 2020年12月24日，下午3:21，Xingbo Huang  写道：
> >
> > +1 (non-binding)
> >
> > - Verify checksums and GPG files
> > - Verify that the source archives do not contains any binaries
> > - Build the source with Maven to ensure all source files have Apache
> > headers (JDK8)
> > Command: mvn clean install -Papache-release
> > - Run e2e tests (JDK8)
> > - Check that all POM files, Dockerfiles, examples point to the same
> > version. That includes the quickstart artifact POM files.
> > - pip install apache_flink_statefun-2.2.2-py3-none-any.whl
> > - Verified NOTICE files in statefun-flink-datastream,
> > statefun-flink-distribution and statefun-ridesharing-example-simulator
> >
> > Best,
> > Xingbo
>
>

Re: [ANNOUNCE] Apache Flink 1.12.0 released

[Yu Li]

Hurray! Thanks everyone who contributed and thanks Robert and Dian for
being our release managers!

Best Regards,
Yu


On Fri, 11 Dec 2020 at 14:56, Congxian Qiu  wrote:

> Thanks Dian and Robert for the great work as release manager, and everyone
> who makes this release possible.
>
> Best,
> Congxian
>
>
> Xintong Song  于2020年12月11日周五 下午1:49写道：
>
> > Congratulations~! Thanks Robert, Dian and everyone.
> >
> > Thank you~
> >
> > Xintong Song
> >
> >
> >
> > On Thu, Dec 10, 2020 at 11:23 PM Robert Metzger 
> > wrote:
> >
> > > Thanks Nick!
> > >
> > > This is blocked on the maintainers of the official images to merge this
> > PR:
> > > https://github.com/docker-library/official-images/pull/9249
> > > I can not really make an estimate when they'll merge it.
> > >
> > > On Thu, Dec 10, 2020 at 4:20 PM nick toker 
> > > wrote:
> > >
> > > > Hi
> > > > first good job  and tank you
> > > >
> > > > i don't find in docker hub the new version 1.12
> > > >
> > > > when it will be there ?
> > > >
> > > > nick
> > > >
> > > > ‫בתאריך יום ה׳, 10 בדצמ׳ 2020 ב-14:17 מאת ‪Robert Metzger‬‏ <‪
> > > > rmetz...@apache.org‬‏>:‬
> > > >
> > > >> The Apache Flink community is very happy to announce the release of
> > > >> Apache Flink 1.12.0, which is the latest major release.
> > > >>
> > > >> Apache Flink® is an open-source stream processing framework for
> > > >> distributed, high-performing, always-available, and accurate data
> > > streaming
> > > >> applications.
> > > >>
> > > >> The release is available for download at:
> > > >> https://flink.apache.org/downloads.html
> > > >>
> > > >> Please check out the release blog post for an overview of the
> > > >> improvements for this bugfix release:
> > > >> https://flink.apache.org/news/2020/12/10/release-1.12.0.html
> > > >>
> > > >> The full release notes are available in Jira:
> > > >>
> > > >>
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522=12348263
> > > >>
> > > >> We would like to thank all contributors of the Apache Flink
> community
> > > who
> > > >> made this release possible!
> > > >>
> > > >> Regards,
> > > >> Dian & Robert
> > > >>
> > > >>
> > >
> >
>

[jira] [Created] (FLINK-20052) kafka/gelly pre-commit test failed due to process hang

[Yu Li (Jira)]

Yu Li created FLINK-20052:
-

 Summary: kafka/gelly pre-commit test failed due to process hang
 Key: FLINK-20052
 URL: https://issues.apache.org/jira/browse/FLINK-20052
 Project: Flink
  Issue Type: Bug
  Components: Library / Graph Processing (Gelly), Tests
Affects Versions: 1.12.0
Reporter: Yu Li
 Fix For: 1.12.0


The kafka/gelly test failed in recent pre-commit [Azure 
build|https://s.apache.org/flink-kafka-gelly-failure]:
{noformat}
Process produced no output for 900 seconds.
...
##[error]Bash exited with code '143'.
{noformat}




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: grant me the permission as a contributor

[Yu Li]

Hi longlai,

Welcome to the Flink community!

You no longer need contributor permissions. You can simply create a JIRA
ticket and ask to be assigned to it in order to start working. Please also
take a look at the Flink's contribution guidelines [1] [2] for more
information.

Best Regards,
Yu

[1] https://flink.apache.org/contributing/how-to-contribute.html
[2]
https://flink.apache.org/contributing/contribute-code.html#create-jira-ticket-and-reach-consensus


On Fri, 30 Oct 2020 at 22:09, longlai li  wrote:

> Hi Guys,
>
> I want to contribute to Apache Flink.Would you please give me the
> permission as a contributor?My JIRA ID is longlai.
>