Re: [DISCUSS] Flink 1.20.2 release

+1 Best Leonard Xu 于2025年5月9日周五 16:32写道： > +1, thanks Ferenc for driving this release. > > Best, > Leonard > > > 2025 5月 9 15:55，Zakelly Lan 写道： > > > > +1 > > > > Thanks for volunteering > > > > > > Best, > > Zakelly > > > > On Fri, May 9, 2025 at 3:42 PM Martijn Visser > > wrote: > > > >> +1

Re: [DISCUSS] Release Flink CDC version 3.4.0

+1 Best Hang Ruan 于2025年4月27日周日 15:22写道： > +1 to release 3.4.0 version. > > Best, > Hang > > On Sun, Apr 27, 2025 at 1:54 PM Leonard Xu wrote: > > > > +1 to release 3.4.0 version, thanks Yanquan for driving the release work. > > > > > > Best, > > Leonard > > > > > 2025 4月 27 12:19，Yanquan Lv 写

Re: [ANNOUNCE] New Apache Flink Committer - Xuyang

Congratulations, Xuyang! Jingsong Li 于2025年2月20日周四 13:18写道： > Congratulations, Xuyang! > > Best, > Jingsong > > On Thu, Feb 20, 2025 at 1:10 PM Sergey Nuyanzin > wrote: > > > > Congratulations, Xuyang! > > > > On Thu, Feb 20, 2025, 04:30 Hongshun Wang > wrote: > > > > > Congratulations, Xuyan

Re: Flink Operator 1.11 release planning

ggestion would be to wrap up current PRs and target mid february for > > the release cut. > > We should also be able to include Flink 2.0 preview support this way :) > > > > What do you think? > > Gyula > -- Best ConradJam

Re: [Discuss] Flink CDC 3.4 Kick Off

+1 Yanquan Lv 于2025年1月22日周三 15:35写道： > Hi devs, > > As FlinkCDC 3.3 was released recently, it's a good time to kick off the > upcoming Flink CDC 3.4 release cycle. > > In past community discussions, we have identified the following demands > that need to be completed: > Bump Flink version to 1.2

Re: Upgrade to Netty 4.x (1.19.2, 1.20.1 releases)

+1 Alexis Sarda-Espinosa 于2025年1月20日周一 18:38写道： > Hello, > > what about io.netty.maxDirectMemory [1]? Is it relevant? I haven't been > able to understand exactly how much that changes, but I find it odd that, > for the default, <"practical max direct memory" would be 2 * max memory as > defined

Re: Memory leak in pekko's Netty 4 transport.

The memory leak is because I forgot the `Bytebuf#release` call. > > > > > > We will try to work out a release soon on 1.1.3 > > > > > > 何品 > > > > > > -- Best ConradJam

Re: Re: [DISCUSS] Flink 1.20.1 release

+1 for a 1.20.1 release , best ~ David Radley 于2024年12月11日周三 00:07写道： > +1 for a 1.20.1 release, Thanks for driving Alex! > > There is a PR [1] against master that fixes a lot of vulnerabilities in > the Web UI, this requires a PR that brings in a later level of Node [2]. We > would like to back

Re: [DISCUSS] Flink 1.20.1 release

volunteer > as the > > > release manager. > > > > > > Best regards, > > > Alex > > > > > > [1] > https://github.com/apache/flink/compare/release-1.20.0...release-1.20 > -- Best ConradJam

Re: Dynamic Iceberg Sink

+1 I have been trying to complete the Flink CDC Iceberg pipeline recently, and this feature has been helpful for my work Ferenc Csaky 于2024年11月14日周四 21:16写道： > Hi Peter, Max, > > Thanks for starting this discussion, +1 for the proposal. I agree > that the added functionality would solve some maj

Re: [DISCUSS] FlinkCDC bump version to Flink 1.19

pache.org/confluence/display/FLINK/FLIP-372%3A+Enhance+and+synchronize+Sink+API+to+match+the+Source+API > [4] https://github.com/apache/iceberg/pull/10179 > [5] https://issues.apache.org/jira/browse/FLINK-32514 > Sorry for resend again due to some issues with the email server. -- Best ConradJam

FLIP-202: Flink Clickhouse Connector to Flink Community

[4] Discussion: https://github.com/itinycheng/flink-connector-clickhouse/issues/102 -- Best ConradJam

Re: [ANNOUNCE] Apache Flink 1.20.0 released

t; > > > > > Flink 1.20.0, which is the first release for the Apache > > Flink 1.20 > > > > > > > > > > series. > > > > > > > > > > > > > > > > > > > > Apache Flink® is an open-source stream processing > > framework for > > > > > > > > > > > > > > > > > > > > distributed, high-performing, always-available, and > > accurate data > > > > > > > > > > streaming > > > > > > > > > > > > > > > > > > > > applications. > > > > > > > > > > > > > > > > > > > > The release is available for download at: > > > > > > > > > > > > > > > > > > > > https://flink.apache.org/downloads.html > > > > > > > > > > > > > > > > > > > > Please check out the release blog post for an overview of > > the > > > > > > > > > > improvements > > > > > > > > > > for this release: > > > > > > > > > > > > > https://flink.apache.org/2024/08/02/announcing-the-release-of-apache-flink-1.20/ > > > > > > > > > > > > > > > The full release notes are available in Jira: > > > > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522&version=12354210 > > > > > > > > > > > > > > > We would like to thank all contributors of the Apache > Flink > > > > > > > > > > community who > > > > > > > > > > > > > > > > > > > > made this release possible! > > > > > > > > > > > > > > > > > > > > Best, > > > > > > > > > > > > > > > > > > > > Robert, Rui, Ufuk, Weijie > > > -- Best ConradJam

Re: [DISCUSS] FLIP-461: FLIP-461: Synchronize rescaling with checkpoint creation to minimize reprocessing

ias > > [1] > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-461%3A+Synchronize+rescaling+with+checkpoint+creation+to+minimize+reprocessing > -- Best ConradJam

Re: [ANNOUNCE] New Apache Flink PMC Member - Weijie Guo

gt;>>> > > > > > >>>> At 2024-06-04 14:45:45, "Xintong Song" > > > > > wrote: > > > > > >>>>> Hi everyone, > > > > > >>>>> > > > > > >>>>> On behalf of the PMC, I'm very happy to announce that Weijie > > Guo > > > > has > > > > > >>>> joined > > > > > >>>>> the Flink PMC! > > > > > >>>>> > > > > > >>>>> Weijie has been an active member of the Apache Flink > community > > > for > > > > many > > > > > >>>>> years. He has made significant contributions in many > > components, > > > > > >>> including > > > > > >>>>> runtime, shuffle, sdk, connectors, etc. He has driven / > > > > participated in > > > > > >>>>> many FLIPs, authored and reviewed hundreds of PRs, been > > > > consistently > > > > > >>>> active > > > > > >>>>> on mailing lists, and also helped with release management of > > 1.20 > > > > and > > > > > >>>>> several other bugfix releases. > > > > > >>>>> > > > > > >>>>> Congratulations and welcome Weijie! > > > > > >>>>> > > > > > >>>>> Best, > > > > > >>>>> > > > > > >>>>> Xintong (on behalf of the Flink PMC) > > > > > >>>> > > > > > >>> > > > > > > > > > > > > > > > > > > -- > > Best, > > Hangxiang. > > > -- Best ConradJam

Re: [DISCUSS] Add Flink CDC Channel to Apache Flink Slack Workspace

gt; > is > > > a sufficiently distinct component > > > within the Apache Flink ecosystem, and having a dedicated channel will > > make > > > it viable and useful for > > > those specifically working with or interested in this technology. > > > > > > Looking forward to your feedback and support on this proposal. > > > > > > > > > Best, > > > Zhongqiang Gong > > > > > -- Best ConradJam

Re: [DISCUSS] Flink CDC 3.1.1 Release

//issues.apache.org/jira/browse/FLINK-35464 > > [3] https://issues.apache.org/jira/browse/FLINK-35149 > > [4] https://issues.apache.org/jira/browse/FLINK-35323 > > [5] https://issues.apache.org/jira/browse/FLINK-35430 > > [6] https://issues.apache.org/jira/browse/FLINK-35447 > > > > -- Best ConradJam

Re: [ANNOUNCE] Apache Flink CDC 3.1.0 released

eNote.jspa?projectId=12315522&version=12354387 > > > > We would like to thank all contributors of the Apache Flink community > > who made this release possible! > > > > Regards, > > Qingsheng Ren > > > -- Best ConradJam

Re: [VOTE] FLIP-447: Upgrade FRocksDB from 6.20.3 to 8.10.0

for at least 72 hours unless there is an > > objection > > > or > > > > insufficient votes. > > > > > > > > [1] > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-447%3A+Upgrade+FRocksDB+from+6.20.3++to+8.10.0 > > > > [2] https://lists.apache.org/thread/lrxjfpjjwlq4sjzm1oolx58n1n8r48hw > > > > > > > > -- > > > > Best, > > > > Yue > > > > > > > > > > -- Best ConradJam

Re: [VOTE] FLIP-446: Kubernetes Operator State Snapshot CRD

less there is an > objection > > or > > > insufficient votes. > > > > > > [1] > > > > > > > > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-446%3A+Kubernetes+Operator+State+Snapshot+CRD > > > [2] https://lists.apache.org/thread/q5dzjwj0qk34rbg2sczyypfhokxoc3q7 > > > > > > Regards, > > > Mate > > > > > > -- Best ConradJam

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

xplore 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

[jira] [Created] (FLINK-34537) Autoscaler JDBC

ConradJam created FLINK-34537: - Summary: Autoscaler JDBC Key: FLINK-34537 URL: https://issues.apache.org/jira/browse/FLINK-34537 Project: Flink Issue Type: Improvement Components

[jira] [Created] (FLINK-34319) Bump okhttp version to 4.12.0

ConradJam created FLINK-34319: - Summary: Bump okhttp version to 4.12.0 Key: FLINK-34319 URL: https://issues.apache.org/jira/browse/FLINK-34319 Project: Flink Issue Type: Improvement

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

> > > > > > > > > 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 > > > > > > > > > > > > > > > > > >>>>>> > > > > > > > > > > > > > > > > > >>>>> > > > > > > > > > > > > > > > > > >>>> > > > > > > > > > > > > > > > > > >>> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- Best ConradJam

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

gt;>>>>> 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 further discussion within the Flink PMC. > > > >>>>>> Additionally, we need to discuss how to migrate existing users > and > > > >>>>>> documents. We have a user group of nearly 10,000 people and a > > > >>>>> multi-version > > > >>>>>> documentation site need to migrate. We also need to plan for the > > > >>>>> migration > > > >>>>>> of CI/CD processes and other specifics. > > > >>>>>>> > > > >>>>>>> > > > >>>>>>> While there are many intricate details that require > > > >> implementation, > > > >>>> we > > > >>>>>> are committed to progressing and finalizing this donation > process. > > > >>>>>>> > > > >>>>>>> > > > >>>>>>> Despite being Flink’s most active ecological project (as > > > >> evaluated > > > >>> by > > > >>>>>> GitHub metrics), it also boasts a significant user base. > However, I > > > >>>>> believe > > > >>>>>> it's essential to commence discussions on future operations only > > > >>> after > > > >>>>> the > > > >>>>>> community reaches a consensus on whether they desire this > donation. > > > >>>>>>> > > > >>>>>>> Really looking forward to hear what you think! > > > >>>>>>> > > > >>>>>>> > > > >>>>>>> > > > >>>>>>> Best, > > > >>>>>>> Leonard (on behalf of the Flink CDC Connectors project > > > >> maintainers) > > > >>>>>>> [1]https://github.com/ververica/flink-cdc-connectors > > > >>>>>>> [2] > > > >>>>>>> > > > >> > > > > https://ververica.github.io/flink-cdc-connectors/master/content/overview/cdc-connectors.html > > > >>>>>>> [3]https://debezium.io > > > >>>>>>> [4] > > > >>>>>>> > > > >> > > > > https://ververica.github.io/flink-cdc-connectors/master/content/overview/cdc-pipeline.html > > > >>>> > > > >>>> -- > > > >>>> Best regards, > > > >>>> Sergey > > > >>>> > -- Best ConradJam

Re: [DISCUSS] Release Flink 1.16.3

of 1.16 > > series. > > > > Best, > > Leonard > > > > > -- > Best regards, > Sergey > -- Best ConradJam

Re: [ANNOUNCE] Apache Flink 1.18.0 released

; > > >>>> wrote: > > > > > > >> > > >>>> > > > > > > >> > > >>>>> Thanks for the great work! Congrats all! > > > > > > >> > > >>>>> > > > > > > >> > > >>>>> Best, > > > > > > >> > > >>>>> Lincoln Lee > > > > > > >> > > >>>>> > > > > > > >> > > >>>>> > > > > > > >> > > >>>>> Jing Ge 于2023年10月27日周五 > > > > > 00:16写道： > > > > > > >> > > >>>>> > > > > > > >> > > >>>>>> The Apache Flink community is very happy to > announce the > > > > > > release of > > > > > > >> > > >>>>> Apache > > > > > > >> > > >>>>>> Flink 1.18.0, which is the first release for the > Apache > > > > > > Flink 1.18 > > > > > > >> > > >>>>> series. > > > > > > >> > > >>>>>> > > > > > > >> > > >>>>>> Apache Flink® is an open-source unified stream and > batch > > > > > data > > > > > > >> > > >>>> processing > > > > > > >> > > >>>>>> framework for distributed, high-performing, > > > > > > always-available, and > > > > > > >> > > >>>>> accurate > > > > > > >> > > >>>>>> data applications. > > > > > > >> > > >>>>>> > > > > > > >> > > >>>>>> The release is available for download at: > > > > > > >> > > >>>>>> https://flink.apache.org/downloads.html > > > > > > >> > > >>>>>> > > > > > > >> > > >>>>>> Please check out the release blog post for an > overview of > > > > > the > > > > > > >> > > >>>>> improvements > > > > > > >> > > >>>>>> for this release: > > > > > > >> > > >>>>>> > > > > > > >> > > >>>>>> > > > > > > >> > > >>>>> > > > > > > >> > > >>>> > > > > > > >> > > >>> > > > > > > >> > > >> > > > > > > >> > > > > > > > > > > > > > > > > > > https://flink.apache.org/2023/10/24/announcing-the-release-of-apache-flink-1.18/ > > > > > > >> > > >>>>>> > > > > > > >> > > >>>>>> The full release notes are available in Jira: > > > > > > >> > > >>>>>> > > > > > > >> > > >>>>>> > > > > > > >> > > >>>>> > > > > > > >> > > >>>> > > > > > > >> > > >>> > > > > > > >> > > >> > > > > > > >> > > > > > > > > > > > > > > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315522&version=12352885 > > > > > > >> > > >>>>>> > > > > > > >> > > >>>>>> We would like to thank all contributors of the > Apache > > > > Flink > > > > > > >> > > >> community > > > > > > >> > > >>>> who > > > > > > >> > > >>>>>> made this release possible! > > > > > > >> > > >>>>>> > > > > > > >> > > >>>>>> Best regards, > > > > > > >> > > >>>>>> Konstantin, Qingsheng, Sergey, and Jing > > > > > > >> > > >>>>>> > > > > > > >> > > >>>>> > > > > > > >> > > >>>> > > > > > > >> > > >>> > > > > > > >> > > >> > > > > > > >> > > > > > > > > >> > > > > > > > > >> > > > > > > >> > > > > > > >> > > > > > > >> -- > > > > > > >> > > > > > > >> Best, > > > > > > >> Benchao Li > > > > > > > > > > > > > > > > -- Best ConradJam

[jira] [Created] (FLINK-33362) Document Externalized Declarative Resource Management With Chinese

ConradJam created FLINK-33362: - Summary: Document Externalized Declarative Resource Management With Chinese Key: FLINK-33362 URL: https://issues.apache.org/jira/browse/FLINK-33362 Project: Flink

Re: [VOTE] FLIP-366: Support standard YAML for FLINK configuration

>> > number of votes). > >> > > >> > Thanks, > >> > Junrui > >> > > >> > [1] > >> > > >> > https://cwiki.apache.org/confluence/display/FLINK/FLIP-366%3A+Support+standard+YAML+for+FLINK+configuration > >> > [2]https://lists.apache.org/thread/qfhcm7h8r5xkv38rtxwkghkrcxg0q7k5 > >> > > >> > >> > -- Best ConradJam

Re: Re: [DISCUSS] FLIP-373: Support Configuring Different State TTLs using SQL Hint

t; > >> > > > >> > > > > https://nightlies.apache.org/flink/flink-docs-master/docs/dev/table/sql/queries/deduplication/ > > > >> [3] > > > >> > > > >> > > > > https://nightlies.apache.org/flink/flink-docs-master/docs/dev/table/sql/queries/topn/ > > > >> > > > >> > > > >> Best, > > > >> Feng > > > >> > > > >> On Sun, Oct 8, 2023 at 5:53 PM Jane Chan > wrote: > > > >> > > > >> > Hi devs, > > > >> > > > > >> > I'd like to initiate a discussion on FLIP-373: Support Configuring > > > >> > Different State TTLs using SQL Hint [1]. This proposal is on top > of > > > the > > > >> > FLIP-292 [2] to address typical scenarios with unambiguous > semantics > > > and > > > >> > hint propagation. > > > >> > > > > >> > I'm looking forward to your opinions! > > > >> > > > > >> > > > > >> > [1] > > > >> > > > > >> > > > > >> > > > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-373%3A+Support+Configuring+Different+State+TTLs+using+SQL+Hint > > > >> > [2] > > > >> > > > > >> > > > > >> > > > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-292%3A+Enhance+COMPILED+PLAN+to+support+operator-level+state+TTL+configuration > > > >> > > > > >> > Best, > > > >> > Jane > > > >> > > > > >> > > > > -- Best ConradJam

Re: [Re-DISCUSS] FLIP-202: Introduce ClickHouse Connector

b.com/itinycheng/flink-connector-clickhouse [3] https://github.com/ClickHouse/clickhouse-java/releases Martijn Visser 于2023年9月20日周三 21:20写道： > Hi ConradJam, > > The FLIP still references the unofficial "flink-clickhouse-connector" > which I don't really understand: you want

Re: [ANNOUNCE] Release 1.18.0, release candidate #0

t; > > > > > > > > > > > On Tue, Sep 19, 2023 at 4:26 PM Zakelly Lan < > > > > > > zakelly@gmail.com > > > > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > Hi everyone, > > > > > > > > > > > > > > > > > > > > > > > > > > I am working on rebuilding the benchmark pipeline > and > > > > it's > > > > > > almost > > > > > > > > > > > > > done. However, due to the change in machines for > > > > > > benchmarking, I > > > > > > > > > will > > > > > > > > > > > > > need a few more days to run tests and gather the > > baseline > > > > > > scores > > > > > > > > > for > > > > > > > > > > > > > further comparison. Once the pipeline is fully > > ready, we > > > > will > > > > > > > > > proceed > > > > > > > > > > > > > with the performance test for release 1.18.0. > > > > > > > > > > > > > > > > > > > > > > > > > > Please let me know if you have any concerns. Thank > > you > > > > all > > > > > > for > > > > > > > > your > > > > > > > > > > > > > patience. > > > > > > > > > > > > > > > > > > > > > > > > > > Best, > > > > > > > > > > > > > Zakelly > > > > > > > > > > > > > > > > > > > > > > > > > > On Mon, Sep 18, 2023 at 6:57 PM Jing Ge > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hi everyone, > > > > > > > > > > > > > > > > > > > > > > > > > > > > The RC0 for Apache Flink 1.18.0 has been created. > > This > > > > RC > > > > > > is > > > > > > > > > > currently > > > > > > > > > > > > > for > > > > > > > > > > > > > > preview only to facilitate the integrated testing > > > > since the > > > > > > > > > > benchmark > > > > > > > > > > > > > tests > > > > > > > > > > > > > > are not available yet[1] and the release > > announcement > > > > is > > > > > > still > > > > > > > > > > under > > > > > > > > > > > > > > review. The RC1 will be released after all > > benchmarks > > > > > > tests are > > > > > > > > > > passed. > > > > > > > > > > > > > The > > > > > > > > > > > > > > related voting process will be triggered once the > > > > > > announcement > > > > > > > > is > > > > > > > > > > > > ready. > > > > > > > > > > > > > > The RC0 has all the artifacts that we would > > typically > > > > have > > > > > > for > > > > > > > > a > > > > > > > > > > > > release, > > > > > > > > > > > > > > except for the release note and the website pull > > > > request > > > > > > for > > > > > > > > the > > > > > > > > > > > > release > > > > > > > > > > > > > > announcement. > > > > > > > > > > > > > > > > > > > > > > > > > > > > The following contents are available for your > > review: > > > > > > > > > > > > > > > > > > > > > > > > > > > > - The preview source release and binary > convenience > > > > > > releases > > > > > > > > [2], > > > > > > > > > > which > > > > > > > > > > > > > > are signed with the key with fingerprint > > > > > > 96AE0E32CBE6E0753CE6 > > > > > > > > > [3]. > > > > > > > > > > > > > > - all artifacts that would normally be deployed > to > > the > > > > > > Maven > > > > > > > > > > > > > > Central Repository [4]. > > > > > > > > > > > > > > - source code tag "release-1.18.0-rc0" [5] > > > > > > > > > > > > > > > > > > > > > > > > > > > > Your help testing the release will be greatly > > > > appreciated! > > > > > > And > > > > > > > > > > we'll > > > > > > > > > > > > > > create the rc1 release and the voting thread as > > soon as > > > > > > all the > > > > > > > > > > efforts > > > > > > > > > > > > > are > > > > > > > > > > > > > > finished. > > > > > > > > > > > > > > > > > > > > > > > > > > > > [1] > > https://issues.apache.org/jira/browse/FLINK-33052 > > > > > > > > > > > > > > [2] > > > > > > > > > > > https://dist.apache.org/repos/dist/dev/flink/flink-1.18.0-rc0/ > > > > > > > > > > > > > > [3] > > > > https://dist.apache.org/repos/dist/release/flink/KEYS > > > > > > > > > > > > > > [4] > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > https://repository.apache.org/content/repositories/orgapacheflink-1656/ > > > > > > > > > > > > > > [5] > > > > > > > > > > > > > > https://github.com/apache/flink/releases/tag/release-1.18.0-rc0 > > > > > > > > > > > > > > > > > > > > > > > > > > > > Best regards, > > > > > > > > > > > > > > Qingsheng, Sergei, Konstantin and Jing > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- Best ConradJam

Re: [VOTE] FLIP-312: Prometheus Sink Connector

+1 (non binding) Samrat Deb 于2023年9月21日周四 23:31写道： > Thank you , > > +1 (non binding) > > Bests, > Samrat > > On Thu, Sep 21, 2023 at 9:43 AM Leonard Xu wrote: > > > Thanks Lorenzo for driving this. > > > > +1(binding) > > > > Best, > > Leonard > > > > > On Sep 21, 2023, at 11:47 AM, Yun Tang

Re: [Discuss] FLIP-366: Support standard YAML for FLINK configuration

gt; > > > > > > By supporting standard YAML, these issues can be resolved, and users > > can > > > > create a Flink configuration file using third-party tools and > leverage > > > > some advanced YAML features. Therefore, we propose to support > standard > > > > YAML for FLINK configuration. > > > > > > > > You can find more details in the FLIP-366[1]. Looking forward to your > > > > feedback. > > > > > > > > [1] > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-366%3A+Support+standard+YAML+for+FLINK+configuration > > > > > > > > Best, > > > > Junrui > > > > > > > > > > -- Best ConradJam

Re: [Re-DISCUSS] FLIP-202: Introduce ClickHouse Connector

Thanks to @Martijn @Leonard for raising this question This is also something I have been worried about, that is, the issue of code copyright ownership and cooperation. That's why I mark FLIP-202 [1] as draft. I have sent a private email inviting the author to participate. If there is more news, I

Re: [DISCUSS] FLIP-367: Support Setting Parallelism for Table/SQL Sources

ka source is bound by the > > number > > > of partitions, any extra tasks would be idle. > > > > - Other operators may involve intensive computation and need a larger > > > parallelism. > > > > > > > > We propose to improve the current situation by extending the current > > > table source API to support setting parallelism for Table/SQL sources > via > > > connector options. > > > > > > > > Looking forward to your feedback. > > > > > > > > [1] FLIP-367: Support Setting Parallelism for Table/SQL Sources - > > Apache > > > Flink - Apache Software Foundation< > > > > > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=263429150 > > > > > > > > [2] FLIP-146: Improve new TableSource and TableSink interfaces - > Apache > > > Flink - Apache Software Foundation< > > > > > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-146%3A+Improve+new+TableSource+and+TableSink+interfaces > > > > > > > > > > > > Best, > > > > Zhanghao Chen > > > > > > > > > > > > -- > > > > > > Best, > > > Benchao Li > > > > > > -- Best ConradJam

Re: [Discuss] CRD for flink sql gateway in the flink k8s operator

t; > > > > > like? > > > > > > > > > > > > Adding a CRD would mean you need to add some operator/controller > > > logic > > > > as > > > > > > well. Why not simply use a Deployment / StatefulSet in > Kubernetes? > > > > > > > > > > > > Or a Helm chart if you want to make it more user friendly? > > > > > > > > > > > > Cheers, > > > > > > Gyula > > > > > > > > > > > > On Thu, Sep 14, 2023 at 12:57 PM Dongwoo Kim < > > dongwoo7@gmail.com > > > > > > > > > > wrote: > > > > > > > > > > > > > Hi all, > > > > > > > > > > > > > > I've been working on setting up a flink SQL gateway in a k8s > > > > > environment > > > > > > > and it got me thinking — what if we had a CRD for this? > > > > > > > > > > > > > > So I have quick questions below. > > > > > > > 1. Is there ongoing work to create a CRD for the Flink SQL > > Gateway? > > > > > > > 2. If not, would the community be open to considering a CRD for > > > this? > > > > > > > > > > > > > > I've noticed a growing demand for simplified setup of the flink > > sql > > > > > > gateway > > > > > > > in flink's slack channel. > > > > > > > Implementing a CRD could make deployments easier and offer > better > > > > > > > integration with k8s. > > > > > > > > > > > > > > If this idea is accepted, I'm open to drafting a FLIP for > further > > > > > > > discussion > > > > > > > > > > > > > > Thanks for your time and looking forward to your thoughts! > > > > > > > > > > > > > > Best regards, > > > > > > > Dongwoo > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- Best ConradJam

Re: [DISSCUSS] Kubernetes Operator Flink Version Support Policy

+1 Yang Wang 于2023年9月14日周四 16:15写道： > Since the users could always use the old Flink Kubernetes Operator version > along with old Flink versions, I am totally in favor of this proposal to > reduce maintenance burden. > > Best, > Yang > > Biao Geng 于2023年9月6日周三 18:15写道： > > > +1 for the proposal

Re: [VOTE] FLIP-361: Improve GC Metrics

Gyula > > [1] > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-361%3A+Improve+GC+Metrics > [2] https://lists.apache.org/thread/qqqv54vyr4gbp63wm2d12q78m8h95xb2 > -- Best ConradJam

Re: [VOTE] FLIP-334: Decoupling autoscaler and kubernetes and support the Standalone Autoscaler

2 > > hours (until Sep 16th 11:00 UTC+8) unless there is an objection or > > insufficient votes. > > > > [1] > > > > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-334+%3A+Decoupling+autoscaler+and+kubernetes+and+support+the+Standalone+Autoscaler > > [2] https://lists.apache.org/thread/kmm03gls1vw4x6vk1ypr9ny9q9522495 > > > > Best, > > Rui > > > -- Best ConradJam

Re: [VOTE] FLIP-323: Support Attached Execution on Flink Application Completion for Batch Jobs

he.org/confluence/display/FLINK/FLIP-323%3A+Support+Attached+Execution+on+Flink+Application+Completion+for+Batch+Jobs > > which proposes to introduce attached execution for batch jobs. The > discussion thread can be found here< > https://lists.apache.org/thread/d3toldk6qqjh2fnbmqthlfkj9rc6lwgl>: > > > Best, > > Allison Chang > > > > > > > -- Best ConradJam

Re: [Re-DISCUSS] FLIP-202: Introduce ClickHouse Connector

Does anyone else have an opinion on this part? If not I will start voting.Comment collection will be open again

Re: [VOTE] FLIP-356: Support Nested Fields Filter Pushdown

+1 (non-binding) Yuepeng Pan 于2023年9月1日周五 15:43写道： > +1 (non-binding) > > Best, > Yuepeng > > > > At 2023-09-01 14:32:19, "Jark Wu" wrote: > >+1 (binding) > > > >Best, > >Jark > > > >> 2023年8月30日 02:40，Venkatakrishnan Sowrirajan 写道： > >> > >> Hi everyone, > >> > >> Thank you all for your feedb

Re: [Re-DISCUSS] FLIP-202: Introduce ClickHouse Connector

k forward to the new design. > > Best regards, > Jing > > On Thu, Aug 24, 2023 at 8:00 AM ConradJam wrote: > > > Hi Community > > > > I want to re-initiate the discussion related to FLIP-202. This is a > > discussion related to the Clickhouse connect

Re: [Re-DISCUSS] FLIP-202: Introduce ClickHouse Connector

hanks for driving it! +1 for starting a new round of discussion based on > > the input you wrote in the comment. Look forward to the new design. > > > > Best regards, > > Jing > > > > On Thu, Aug 24, 2023 at 8:00 AM ConradJam wrote: > > > > > Hi C

[Re-DISCUSS] FLIP-202: Introduce ClickHouse Connector

ira/browse/FLINK-26999> ：Introduce ClickHouse Connector -- Best ConradJam

Re: [DISCUSS] Update Flink Roadmap

;> > >>>> Best regards, > > >>> > >> > >>>> Jing > > >>> > >> > >>>> > > >>> > >> > >>>> On Thu, Jun 1, 2023 at 3:31 PM Jark Wu > > > >>> wrote: > > >>> > >> > >>>> > > >>> > >> > >>>>> Hi all, > > >>> > >> > >>>>> > > >>> > >> > >>>>> Martijn and I would like to initiate a discussion on the > > >>> Flink > > >>> > >> > >> roadmap, > > >>> > >> > >>>>> which should cover the project's long-term roadmap and > the > > >>> > regular > > >>> > >> > >>> update > > >>> > >> > >>>>> mechanism. > > >>> > >> > >>>>> > > >>> > >> > >>>>> Xintong has already started a discussion about Flink 2.0 > > >>> > planning. > > >>> > >> > >> One > > >>> > >> > >>> of > > >>> > >> > >>>>> the points raised in that discussion is that we should > > have > > >>> a > > >>> > >> > >>> high-level > > >>> > >> > >>>>> discussion of the roadmap to present where the project > is > > >>> > heading > > >>> > >> > >>> (which > > >>> > >> > >>>>> doesn't necessarily need to block the Flink 2.0 > planning). > > >>> > >> Moreover, > > >>> > >> > >>> the > > >>> > >> > >>>>> roadmap on the Flink website [1] hasn't been updated for > > >>> half a > > >>> > >> year, > > >>> > >> > >>> and > > >>> > >> > >>>>> the last update was for the feature radar for the 1.15 > > >>> release. > > >>> > It > > >>> > >> > >> has > > >>> > >> > >>>> been > > >>> > >> > >>>>> 2 years since the community discussed Flink's overall > > >>> roadmap. > > >>> > >> > >>>>> > > >>> > >> > >>>>> I would like to raise two topics for discussion: > > >>> > >> > >>>>> > > >>> > >> > >>>>> 1. The new roadmap. This should be an updated version of > > the > > >>> > >> current > > >>> > >> > >>>>> roadmap[1]. > > >>> > >> > >>>>> 2. A mechanism to regularly discuss and update the > > roadmap. > > >>> > >> > >>>>> > > >>> > >> > >>>>> To make the first topic discussion more efficient, > Martijn > > >>> and I > > >>> > >> > >>>> volunteer > > >>> > >> > >>>>> to summarize the ongoing big things of different > > components > > >>> and > > >>> > >> > >>> present a > > >>> > >> > >>>>> roadmap draft to the community in the next few weeks. > This > > >>> > should > > >>> > >> be > > >>> > >> > >> a > > >>> > >> > >>>> good > > >>> > >> > >>>>> starting point for a more detailed discussion. > > >>> > >> > >>>>> > > >>> > >> > >>>>> Regarding the regular update mechanism, there was a > > >>> proposal in > > >>> > a > > >>> > >> > >>> thread > > >>> > >> > >>>>> [2] three years ago to make the release manager > > responsible > > >>> for > > >>> > >> > >>> updating > > >>> > >> > >>>>> the roadmap. However, it appears that this was not > > >>> documented > > >>> > as a > > >>> > >> > >>>> release > > >>> > >> > >>>>> management task [3], and the roadmap update wasn't > > >>> performed for > > >>> > >> > >>> releases > > >>> > >> > >>>>> 1.16 and 1.17. > > >>> > >> > >>>>> > > >>> > >> > >>>>> In my opinion, making release managers responsible for > > >>> keeping > > >>> > the > > >>> > >> > >>>> roadmap > > >>> > >> > >>>>> up to date is a good idea. Specifically, release > managers > > of > > >>> > >> release > > >>> > >> > >> X > > >>> > >> > >>>> can > > >>> > >> > >>>>> kick off the roadmap update at the beginning of release > X, > > >>> which > > >>> > >> can > > >>> > >> > >>> be a > > >>> > >> > >>>>> joint task with collecting a feature list [4]. > > Additionally, > > >>> > >> release > > >>> > >> > >>>>> managers of release X-1 can help verify and remove the > > >>> > >> accomplished > > >>> > >> > >>> items > > >>> > >> > >>>>> from the roadmap and update the feature radar. > > >>> > >> > >>>>> > > >>> > >> > >>>>> What do you think? Do you have other ideas? > > >>> > >> > >>>>> > > >>> > >> > >>>>> Best, > > >>> > >> > >>>>> Jark & Martijn > > >>> > >> > >>>>> > > >>> > >> > >>>>> [1]: https://flink.apache.org/roadmap.html > > >>> > >> > >>>>> [2]: > > >>> > >> > >> > > >>> https://lists.apache.org/thread/o0l3cg6yphxwrww0k7215jgtw3yfoybv > > >>> > >> > >>>>> [3]: > > >>> > >> > >>>>> > > >>> > >> > >>>> > > >>> > >> > >>> > > >>> > >> > >> > > >>> > >> > > > >>> > >> > > >>> > > > >>> > > > https://cwiki.apache.org/confluence/display/FLINK/Flink+Release+Management > > >>> > >> > >>>>> [4]: > > >>> > >> https://cwiki.apache.org/confluence/display/FLINK/1.18+Release > > >>> > >> > >>>>> > > >>> > >> > >>>> > > >>> > >> > >>> > > >>> > >> > >> > > >>> > >> > > > >>> > >> > > > >>> > >> > > >>> > > > > >>> > > > >>> > > >> > > >> > > > -- Best ConradJam

Re: [ANNOUNCE] New Apache Flink Committer - Yanfei Lei

; > > > > > > > > > > > > > > > > Best, > > > > > > > > > > Qingsheng > > > > > > > > > > > > > > > > > > > > On Mon, Aug 7, 2023 at 4:19 PM Matthias Pohl < > > > > > matthias.p...@aiven.io > > > > > > > > > > .invalid> > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > Congratulations, Yanfei! :) > > > > > > > > > > > > > > > > > > > > On Mon, Aug 7, 2023 at 10:00 AM Junrui Lee < > > > > jrlee@gmail.com> > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > Congratulations Yanfei! > > > > > > > > > > > > > > > > > > > > Best, > > > > > > > > > > Junrui > > > > > > > > > > > > > > > > > > > > Yun Tang 于2023年8月7日周一 15:19写道： > > > > > > > > > > > > > > > > > > > > Congratulations, Yanfei! > > > > > > > > > > > > > > > > > > > > Best > > > > > > > > > > Yun Tang > > > > > > > > > > > > > > > > > > > > From: Danny Cranmer > > > > > > > > > > Sent: Monday, August 7, 2023 15:10 > > > > > > > > > > To: dev > > > > > > > > > > Subject: Re: [ANNOUNCE] New Apache Flink Committer - > Yanfei > > > Lei > > > > > > > > > > > > > > > > > > > > Congrats Yanfei! Welcome to the team. > > > > > > > > > > > > > > > > > > > > Danny > > > > > > > > > > > > > > > > > > > > On Mon, 7 Aug 2023, 08:03 Rui Fan, <1996fan...@gmail.com > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > Congratulations Yanfei! > > > > > > > > > > > > > > > > > > > > Best, > > > > > > > > > > Rui > > > > > > > > > > > > > > > > > > > > On Mon, Aug 7, 2023 at 2:56 PM Yuan Mei < > > > > yuanmei.w...@gmail.com> > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > > On behalf of the PMC, I'm happy to announce Yanfei Lei > as a > > > new > > > > > > > > > > Flink > > > > > > > > > > Committer. > > > > > > > > > > > > > > > > > > > > Yanfei has been active in the Flink community for almost > > two > > > > > > > > > > years > > > > > > > > > > and > > > > > > > > > > has > > > > > > > > > > played an important role in developing and maintaining > > State > > > > > > > > > > and > > > > > > > > > > Checkpoint > > > > > > > > > > related features/components, including RocksDB Rescaling > > > > > > > > > > Performance > > > > > > > > > > Improvement and Generic Incremental Checkpoints. > > > > > > > > > > > > > > > > > > > > Yanfei also helps improve community infrastructure in > many > > > > > > > > > > ways, > > > > > > > > > > including > > > > > > > > > > migrating the Flink Daily performance benchmark to the > > Apache > > > > > > > > > > Flink > > > > > > > > > > slack > > > > > > > > > > channel. She is the maintainer of the benchmark and has > > > > > > > > > > improved > > > > > > > > > > its > > > > > > > > > > detection stability significantly. She is also one of the > > > major > > > > > > > > > > maintainers > > > > > > > > > > of the FrocksDB Repo and released FRocksDB 6.20.3 (part > of > > > > > > > > > > Flink > > > > > > > > > > 1.17 > > > > > > > > > > release). Yanfei is a very active community member, > > > supporting > > > > > > > > > > users > > > > > > > > > > and > > > > > > > > > > participating > > > > > > > > > > in tons of discussions on the mailing lists. > > > > > > > > > > > > > > > > > > > > Please join me in congratulating Yanfei for becoming a > > Flink > > > > > > > > > > Committer! > > > > > > > > > > > > > > > > > > > > Thanks, > > > > > > > > > > Yuan Mei (on behalf of the Flink PMC) > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > Best, > > > Benchao Li > > > > > > -- Best ConradJam

Re: [ANNOUNCE] New Apache Flink Committer - Hangxiang Yu

> Flink > > > > > > > >Committer. > > > > > > > > > > > > > > > >Hangxiang has been active in the Flink community for more than > > 1.5 > > > > > years > > > > > > > >and has played an important role in developing and maintaining > > > State > > > > > and > > > > > > > >Checkpoint related features/components, including Generic > > > > Incremental > > > > > > > >Checkpoints (take great efforts to make the feature > prod-ready). > > > > > Hangxiang > > > > > > > >is also the main driver of the FLIP-263: Resolving schema > > > > > compatibility. > > > > > > > > > > > > > > > >Hangxiang is passionate about the Flink community. Besides the > > > > > technical > > > > > > > >contribution above, he is also actively promoting Flink: talks > > > about > > > > > > > Generic > > > > > > > >Incremental Checkpoints in Flink Forward and Meet-up. > Hangxiang > > > also > > > > > spent > > > > > > > >a good amount of time supporting users, participating in > > > > Jira/mailing > > > > > list > > > > > > > >discussions, and reviewing code. > > > > > > > > > > > > > > > >Please join me in congratulating Hangxiang for becoming a > Flink > > > > > Committer! > > > > > > > > > > > > > > > >Thanks, > > > > > > > >Yuan Mei (on behalf of the Flink PMC) > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > Best, > > > Benchao Li > > > > > > -- Best ConradJam

Re: [VOTE][2.0] FLIP-340: Remove rescale REST endpoint

gt; > > > >>> > > > > >>> On Mon, Jul 24, 2023 at 1:10 PM Chesnay Schepler < > ches...@apache.org > > > > > > > > >>> wrote: > > > > >>> > > > > >>>> Hello, > > > > >>>> > > > > >>>> I'd like to start a vote on FLIP-340. > > > > >>>> > > > > >>>> Discussion thread: > > > > >>>> > https://lists.apache.org/thread/zkslk0qzttwgs8j3s951rht3v1tsyqqk > > > > >>>> FLIP: > > > > >>>> > > > > >>>> > > > > >> > > > > > > > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-340%3A+Remove+rescale+REST+endpoint > > > > >>>> Regards, > > > > >>>> Chesnay > > > > >>>> > > > > >> > > > > >> -- > > > > >> https://twitter.com/snntrable > > > > >> https://github.com/knaufk > > > > >> > > > > > > > > > > > > -- Best ConradJam

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

> >> > >> > >> > >> > >> > >> > >> > >> > >> 在 2023-07-24 11:03:30，"Paul Lam" 写道： > >> >Congrats, Shammon! > >> > > >> >Best, > >> >Paul Lam > >> > > >> >> 2023年7月24日 10:56，Jingsong Li 写道： > >> >> > >> >> Shammon > >> > > >> > -- Best ConradJam

Re: Kubernetes Operator 1.6.0 release planning

te: > >>>> > >>>>> Hi Devs! > >>>>> > >>>>> Based on our release schedule, it is about time for the next Flink > K8s > >>>>> Operator minor release. > >>>>> > >>>>> There are still some minor work items to be completed this week, but > I > >>>>> suggest aiming for next Wednesday (July 26th) as the 1.6.0 > release-cut > >>> - > >>>>> RC1 date. > >>>>> > >>>>> I am volunteering as the release manager but if someone else wants to > >>> do > >>>>> it, I would also be happy to simply give assistance :) > >>>>> > >>>>> Please let me know if you agree or disagree with the suggested > >>> timeline. > >>>>> > >>>>> Cheers, > >>>>> Gyula > >>>>> > >>>> > >>> > > > > -- Best ConradJam

Re: [DISCUSS][2.0] FLIP-337: Remove JarRequestBody#programArgs

;>>> On Thu, Jul 13, 2023 at 9:34 PM Chesnay Schepler < > ches...@apache.org> > > >>>> wrote: > > >>>> > > >>>>> Hello, > > >>>>> > > >>>>> The request body for the jar run/plan REST endpoints accepts > program > > >>>>> arguments as a string (programArgs) or a list of strings > > >>>>> (programArgsList). The latter was introduced as kept running into > > issues > > >>>>> with splitting the string into individual arguments./ > > >>>>> / > > >>>>> > > >>>>> We ideally force users to use the list argument, and we can > simplify > > the > > >>>>> codebase if there'd only be 1 way to pass arguments. > > >>>>> > > >>>>> As such I propose to remove the programArgs field from the request > > body. > > >>>>> > > >>>>> > > >>>> > > > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=263424796 > > >>>>> > > >>>>> Regards, > > >>>>> > > >>>>> Chesnay > > >>>>> > > >> > > > > > > > > -- Best ConradJam

Re: [DISCUSS][2.0] FLIP-340: Remove rescale REST endpoint

+1 Zhu Zhu 于2023年7月19日周三 10:53写道： > +1 > > Thanks, > Zhu > > Jing Ge 于2023年7月18日周二 19:09写道： > > > > +1 > > > > On Tue, Jul 18, 2023 at 1:05 PM Maximilian Michels > wrote: > > > > > +1 > > > > > > On Tue, Jul 18, 2023 at 12:29 PM Gyula Fóra wrote: > > > > > > > > +1 > > > > > > > > On Tue, 18

Re: [VOTE] FLIP-322 Cooldown period for adaptive scheduler

+1 (no-binding) Etienne Chauchot 于2023年7月3日周一 15:57写道： > Hi all, > > The vote closes within 6 hours and, as for now, there was no vote. This > is a very short FLIP, that takes a few minutes to read. > > Please cast your vote so that the development could start. > > Thanks. > > Best > > Etienne >

Re: [VOTE] FLIP-321: introduce an API deprecation process

+1 (no-binding) Matthias Pohl 于2023年7月3日周一 22:33写道： > Thanks, Becket > > +1 (binding) > > On Mon, Jul 3, 2023 at 10:44 AM Jing Ge > wrote: > > > +1(binding) > > > > On Mon, Jul 3, 2023 at 10:19 AM Stefan Richter > > wrote: > > > > > +1 (binding) > > > > > > > > > > On 3. Jul 2023, at 10:08, Ma

Re: [DISCUSS] Release 2.0 Work Items

t;>>>>>>> > >>>>>>>>- In the beginning, we planned to do an in-place refactor of > >>>>>>> DataStream > >>>>>>>>API, until the API migration period is proposed. > >>>>>>>>- Then we want to make it an entirely separate API to > >>>> DataStream, > >>>>>> and > >>>>>>>>listed as a must-have for release 2.0 so that we can remove > >>>>>> DataStream > >>>>>>>> once > >>>>>>>>it's ready. > >>>>>>>>- However, depending on the outcome of the API compatibility > >>>>>>> discussion > >>>>>>>>[1], we may not be able to remove DataStream in 2.0 anyway, > >>>> which > >>>>>>> means > >>>>>>>> we > >>>>>>>>might need to re-evaluate the necessity of this item for 2.0. > >>>>>>>> > >>>>>>>> I'd say we wait a bit longer for the compatibility discussion [1] > >>>> and > >>>>>>>> decide the priority for this item afterwards. > >>>>>>>> > >>>>>>>> > >>>>>>>> Best, > >>>>>>>> > >>>>>>>> Xintong > >>>>>>>> > >>>>>>>> > >>>>>>>> [1] https://lists.apache.org/list.html?dev@flink.apache.org > >>>>>>>> > >>>>>>>> > >>>>>>>> On Mon, Jun 26, 2023 at 6:00 PM Chesnay Schepler < > >>>> ches...@apache.org > >>>>>>>> wrote: > >>>>>>>> > >>>>>>>>> by-and-large I'm quite happy with the list of items. > >>>>>>>>> > >>>>>>>>> I'm curious as to why the "Disaggregated State Management" item > >>>> is > >>>>>>> marked > >>>>>>>>> as a must-have; will it require changes that break something? > >>>> What > >>>>>>>> prevents > >>>>>>>>> it from being added in 2.1? > >>>>>>>>> > >>>>>>>>> We may want to update the Java 17 item to "Make Java 17 the > >>>>> default, > >>>>>>> drop > >>>>>>>>> Java 8/11". Maybe even split it into a must-have "Drop Java 8" > >>>> and > >>>>> a > >>>>>>>>> nice-to-have "Drop Java 11"? > >>>>>>>>> > >>>>>>>>> "Move Calcite rules from Scala to Java": I would hope that this > >>>>> would > >>>>>>> be > >>>>>>>>> an entirely internal change, and could thus be an incremental > >>>>> process > >>>>>>>>> independent of major releases. > >>>>>>>>> What is the actual scale of this item; how much are we actually > >>>>>>>> re-writing? > >>>>>>>>> "Add MetricGroup#getLogicalScope": I'd raise this to a > >>>> must-have; i > >>>>>>> think > >>>>>>>>> I marked it down as nice-to-have only because it depends on > >>>> another > >>>>>>> item. > >>>>>>>>> The ProcessFunction API item is giving me the most headaches > >>>>> because > >>>>>>> it's > >>>>>>>>> very unclear what it actually entails; like is it an entirely > >>>>>> separate > >>>>>>>> API > >>>>>>>>> to DataStream (sounds like it is!) or an extension of DataStream. > >>>>> How > >>>>>>>> much > >>>>>>>>> will it share the internals with DataStream etc.; how does it > >>>>> relate > >>>>>> to > >>>>>>>> the > >>>>>>>>> Table API (w.r.t. switching APIs / what Table API uses > >>>> underneath). > >>>>>>>>> There are a few items I added as ideas which don't have a > >>>> priority > >>>>>> yet; > >>>>>>>>> would love to get some feedback on those. > >>>>>>>>> > >>>>>>>>> On 21/06/2023 08:41, Xintong Song wrote: > >>>>>>>>> > >>>>>>>>> Hi devs, > >>>>>>>>> > >>>>>>>>> As previously discussed in [1], we had been collecting work item > >>>>>>>> proposals > >>>>>>>>> for the 2.0 release until June 15th, on the wiki page [2]. > >>>>>>>>> > >>>>>>>>>- As we have passed the due date, I'd like to kindly remind > >>>>>> everyone > >>>>>>>> *not > >>>>>>>>>to add / remove items directly on the wiki page*. If needed, > >>>>>> please > >>>>>>>> post > >>>>>>>>>in this thread or reach out to the release managers instead. > >>>>>>>>>- I've reached out to some folks for clarifications about > >>>> their > >>>>>>>>>proposals. Some of them mentioned that they can not yet tell > >>>>>> whether > >>>>>>>> we > >>>>>>>>>should do an item or not, and would need more time / > >>>> discussions > >>>>>> to > >>>>>>>> make > >>>>>>>>>the decision. So I added a new symbol for items whose > >>>> priorities > >>>>>> are > >>>>>>>> `TBD`. > >>>>>>>>> Now it's time to collaboratively decide a minimum set of > >>>> must-have > >>>>>>> items. > >>>>>>>>> I've gone through the entire list of proposed items, and found > >>>> most > >>>>>> of > >>>>>>>> them > >>>>>>>>> make quite much sense. So I think an online sync might not be > >>>>>> necessary > >>>>>>>> for > >>>>>>>>> this. I'd like to go with this DISCUSS thread, where everyone can > >>>>>>> comment > >>>>>>>>> on how they think the list can be improved, followed by a VOTE to > >>>>>>>> formally > >>>>>>>>> make the decision. > >>>>>>>>> > >>>>>>>>> Any feedback and opinions, including but not limited to the > >>>>> following > >>>>>>>>> aspects, will be appreciated. > >>>>>>>>> > >>>>>>>>>- Important items that are missing from the list > >>>>>>>>>- Concerns regarding the listed items or their priorities > >>>>>>>>> > >>>>>>>>> Looking forward to your feedback. > >>>>>>>>> > >>>>>>>>> Best, > >>>>>>>>> > >>>>>>>>> Xintong > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> [1] > >>>> > >> > https://lists.apache.org/list?dev@flink.apache.org:lte=1M:release%202.0%20status%20updates > >>>>>>>>> [2] > >>>> https://cwiki.apache.org/confluence/display/FLINK/2.0+Release > >>>>>>>>> > >>>>>>>>> > >>>> > >>>> -- > >>>> Best regards, > >>>> Sergey > >>>> > >> > >> > > -- Best ConradJam

Re: [DISCUSS] FLIP-317: Upgrade Kryo from 2.24.0 to 5.5.0

d to > >>> be tested. > >>> > >>> - Is this worth pursuing or is the Flink project looking to go in a > >>> different direction? I'd like to do some more work on the pull request if > >>> this is being seriously considered for adoption. > >>> > >>> I'm looking forward to hearing everyone's feedback and suggestions. > >>> > >>> Thank you, > >>> Kurt > >>> > >>> [1] > >>> https://cwiki.apache.org/confluence/display/FLINK/FLIP-317%3A+Upgrade+Kryo+from+2.24.0+to+5.5.0 > >> > >> -- > >> Ken Krugler > >> http://www.scaleunlimited.com > >> Custom big data solutions > >> Flink, Pinot, Solr, Elasticsearch > >> > -- Best ConradJam

[jira] [Created] (FLINK-32243) Bump okhttp version to 4.11.0

ConradJam created FLINK-32243: - Summary: Bump okhttp version to 4.11.0 Key: FLINK-32243 URL: https://issues.apache.org/jira/browse/FLINK-32243 Project: Flink Issue Type: Improvement

Re: [DISCUSS] Planning Flink 2.0

ich we can keep developing and release 1.x releases. The > version on the master branch will then become '2.0-SNAPSHOT'. > > > Release Manager > > > Given the new and to-be-explored release process, longer cycle and higher > synchronization requirements, we'd expect the 2.0 release to be more > challenging than previous 1.x releases. Therefore, we'd like to propose to > assemble a release management team with 4-5 experienced PMC members. Jark > and I would like to volunteer as 2 of the release managers. > > > Looking forward to your thoughts. > > > Best, > > Jark & Xintong > > > [1] > https://docs.google.com/document/d/1_PMGl5RuDQGlV99_gL3y7OiRsF0DgCk91Coua6hFXhE/edit?usp=sharing -- Best ConradJam

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

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 -- Best ConradJam

RIC Incremental and GIC Incremental checkpoint use question

Hi Community . I would like to consult about some configurations of Rocksdb incremental checkpoints and GIC. In Flink 1.17,I want to try this feature . If Generic Incremental Checkpoint (GIC) enable, rocksdb Incremental Checkpoint can be disable or enable, Do they both have conflicting switches, do

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

+1 (no-binding) + verify signatures and checksums + build Flink from source (from the src archive) + run simple job flink on k8s application mode and session cluster Robert Metzger 于2023年3月21日周二 20:36写道： > +1 (binding) > > + Started Flink locally with the changelog statebackend + rocksdb again

Re: [DISCUSS] FLIP-301: Hybrid Shuffle supports Remote Storage

RSS, it will simplify our > operation work. > -- Best ConradJam

Re: [VOTE] FLIP-293: Introduce Flink Jdbc Driver For Sql Gateway

ection or insufficient vote. Thank you all. > > > > > > > > > [1] > > > > > > > > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-293%3A+Introduce+Flink+Jdbc+Driver+For+Sql+Gateway > > > [2] https://lists.apache.org/thread/d1owrg8zh77v0xygcpb93fxt0jpjdkb3 > > > > > > > > > Best, > > > Shammon.FY > > > > > > -- Best ConradJam

Re: [Discussion] - Release major Flink version to support JDK 17 (LTS)

ately. > Monitoring: NICE Actimize may monitor incoming and outgoing e-mails. > Viruses: Although we have taken steps toward ensuring that this e-mail and > attachments are free from any virus, we advise that in keeping with good > computing practice the recipient should ensure they are actually virus free. > -- Best ConradJam

Re: [VOTE] FLIP-297: Improve Auxiliary Sql Statements

> > > > > > > The vote will last for at least 72 hours (03/09, 19:30 UTC+8) > > > > unless there is an objection or insufficient votes. Thank you all. > > > > > > > > [1] > > > > > > > > > > > > > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-297%3A+Improve+Auxiliary+Sql+Statements > > > > [2] https://lists.apache.org/thread/54fyd27m8on1cf3hn6dz564zqmkobjyd > > > > > > > > Best Regards, > > > > Ran Tao > > > > https://github.com/chucheng92 > > > > > > > > > > -- Best ConradJam

Re: [VOTE] FLIP-291: Externalized Declarative Resource Management

fluence/display/FLINK/FLIP-291%3A+Externalized+Declarative+Resource+Management > > Best, > D. > -- Best ConradJam

Re: Re: [DISCUSS] Extract core autoscaling algorithm as new SubModule in flink-kubernetes-operator

+1 Maximilian Michels 于2023年2月21日周二 00:21写道： > Great to see the interest here! I think the next step would be to > write a FLIP which explains how the autoscaler implementation would be > made agnostic to the resource management framework (k8s / yarn / etc). > There will have to be platform-agno

Re: [DISCUSS] Release Flink 1.15.4

+1 Sergey Nuyanzin 于2023年2月16日周四 17:36写道： > +1 > > On Thu, Feb 16, 2023 at 10:32 AM yuxia > wrote: > > > +1 > > > > Best regards, > > Yuxia > > > > - 原始邮件 - > > 发件人: "Rui Fan" <1996fan...@gmail.com> > > 收件人: "dev" > > 发送时间: 星期四, 2023年 2 月 16日 上午 11:31:49 > > 主题: Re: [DISCUSS] Release F

Re: [ANNOUNCE] New Apache Flink PMC Member - Dong Lin

announce Dong Lin as a new > > >>>> Flink PMC. > > >>>> > > >>>> Dong is currently the main driver of Flink ML. He reviewed a large > > >>>> number of Flink ML related PRs and also participated in many Flink > ML > > >>>> improvements, such as "FLIP-173","FLIP-174" etc. At the same time, > he > > made > > >>>> a lot of evangelism events contributions for the Flink ML ecosystem. > > >>>> In fact, in addition to the Flink machine learning field, Dong has > > >>> also > > >>>> participated in many other improvements in Flink, such as > "FLIP-205", > > >>>> "FLIP-266","FLIP-269","FLIP-274" etc. > > >>>> Please join me in congratulating Dong Lin for becoming a Flink > PMC! > > >>>> > > >>>> Best, > > >>>> Guowei(on behalf of the Flink PMC) > > >>> > > >> > > >> > > >> -- > > >> Best regards, > > >> Sergey > > > > > -- Best ConradJam

Re: [ANNOUNCE] New Apache Flink Committer - Jing Ge

Dong Lin > >>>>> Sent: Wednesday, February 15, 2023 19:40 > >>>>> To: dev@flink.apache.org > >>>>> Subject: Re: [ANNOUNCE] New Apache Flink Committer - Jing Ge > >>>>> > >>>>> Congratulations Jing! > >>>>> > >>>>> On Wed, Feb 15, 2023 at 12:48 PM Shiwei Wang > >>>> wrote: > >>>>>> Congratulations Jing! > >>>>>> > >>>>>> > >>>>>> > >>>>>>> 在 2023年2月14日，16:00，weijie guo 写道： > >>>>>>> > >>>>>>> Congratulations Jing! > > -- Best ConradJam

Re: [DISCUSS] FLIP-291: Externalized Declarative Resource Management

nt > [2] https://lists.apache.org/thread/2f7dgr88xtbmsohtr0f6wmsvw8sw04f5 > [3] https://github.com/tillrohrmann/flink/tree/autoscaling > [4] https://drive.google.com/file/d/1Vp8W-7Zk_iKXPTAiBT-eLPmCMd_I57Ty/view > > Best, > D. > -- Best ConradJam

Re: [VOTE] FLIP-285: Refactoring LeaderElection to make Flink support multi-component leader election out-of-the-box

aivencloud> < > https://www.facebook.com/aivencloud/> > <https://www.linkedin.com/company/aiven/> > <https://www.linkedin.com/company/aiven><https://twitter.com/aiven_io> > <https://twitter.com/aiven_io> > > Aiven Deutschland GmbH > > Immanuelkirchstraße 26, 10405 Berlin > > Geschäftsführer: Oskari Saarenmaa & Hannu Valtonen > > Amtsgericht Charlottenburg, HRB 209739 B > -- Best ConradJam

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

release/flink/KEYS > [4] https://repository.apache.org/content/repositories/orgapacheflink-1580 > [5] https://github.com/apache/flink/releases/tag/release-1.16.1-rc1 > [6] https://github.com/apache/flink-web/pull/603 > -- Best ConradJam

Re: Reworking the Rescale API

> available prior to restarting the job. > > I've created an issue here: > https://issues.apache.org/jira/browse/FLINK-30773 > > Any comments or interest in working on this? > > -Max > > [1] https://issues.apache.org/jira/browse/FLINK-12312 > [2] > https://cwiki.apache.org/confluence/display/FLINK/FLIP-271%3A+Autoscaling > -- Best ConradJam

Re: Reworking the Rescale API

are > available prior to restarting the job. > > I've created an issue here: > https://issues.apache.org/jira/browse/FLINK-30773 > > Any comments or interest in working on this? > > -Max > > [1] https://issues.apache.org/jira/browse/FLINK-12312 > [2] > htt

Re: [VOTE] FLIP-290: Operator state compression (FLINK-30113)

or not enough votes. > > > > > > > > Best > > > > > > > > Etienne > > > > > > > > > > > > (1) https://lists.apache.org/thread/mor8vtc8s1w53mq884l80y3nt6zybw1w > > > > > > > > (2) > > > > > > > > > > https://cwiki.apache.org/confluence/display/FLINK/FLIP-290+Operator+state+compression > > > > > > > > > > -- Best ConradJam

Re: [DISCUSS] FLIP-290: Operator state compression (FLINK-30113)

; > https://cwiki.apache.org/confluence/display/FLINK/FLIP-290+Operator+state+compression > > > > > > [2] https://github.com/apache/flink/pull/21636 > > > > > > Best, > > > > Etienne > > > -- Best ConradJam

Re: [DISCUSS] Release new FRocksDB

+1 , I agree to open a 7.x branch to study whether the new version of rocksdb has brought something new changes Yun Tang 于2022年12月20日周二 12:47写道： > +1 to have a new FrocksDB release and thanks for the effors. > > For FLINK-24932, we planned to upgrade to RocksDB-6.29.x to support Apple > ARM chip

Re: [DISCUSS] Release Flink 1.16.1

Hi Martijn, FLINK-30116 After merge.Flink Web Ui Configuration Can't show it,I checked the data returned by the back end and there is no problem, but there is an error in the front end, as shown in the picture below, can someone take a look befor

Re: [VOTE] Update Flink's Scala 2.12 support from 2.12.7 to 2.12.16

+1 (non-binding) Sergey Nuyanzin 于2022年12月18日周日 15:42写道： > +1 (non-binding) > > On Sat, Dec 17, 2022 at 1:06 PM David Anderson > wrote: > > > +1 (binding) > > > > > > > > On Fri, Dec 16, 2022 at 12:22 PM Martijn Visser < > martijnvis...@apache.org> > > wrote: > > > > > Hi all, > > > > > > I'm b

Re: [DISCUSS] FLIP-271: Autoscaling

t; >>

Re: [DISCUSS] Release Flink 1.16.1

e also a number of open issues with a fixVersion set to 1.16.1, so > it would be good to understand what the community thinks of starting a > release or if there are some fixes that should be included with 1.16.1. > > Best regards, > > Martijn > > [1] https://issues.apache.org/jira/browse/FLINK-30116 > -- Best ConradJam

[jira] [Created] (FLINK-29544) Update Flink doc

ConradJam created FLINK-29544: - Summary: Update Flink doc Key: FLINK-29544 URL: https://issues.apache.org/jira/browse/FLINK-29544 Project: Flink Issue Type: Sub-task Components

[jira] [Created] (FLINK-29543) Jar Run Rest Handler Support Flink Configuration

ConradJam created FLINK-29543: - Summary: Jar Run Rest Handler Support Flink Configuration Key: FLINK-29543 URL: https://issues.apache.org/jira/browse/FLINK-29543 Project: Flink Issue Type: Sub

[jira] [Created] (FLINK-28574) Bump the fabric8 kubernetes-client to 6.0.0

ConradJam created FLINK-28574: - Summary: Bump the fabric8 kubernetes-client to 6.0.0 Key: FLINK-28574 URL: https://issues.apache.org/jira/browse/FLINK-28574 Project: Flink Issue Type: Bug

[jira] [Created] (FLINK-27943) Link Kubernetes Operator RoadMap Page To Flink RoadMap Page Web Site

ConradJam created FLINK-27943: - Summary: Link Kubernetes Operator RoadMap Page To Flink RoadMap Page Web Site Key: FLINK-27943 URL: https://issues.apache.org/jira/browse/FLINK-27943 Project: Flink