+1, thanks for driving.
Best,
Ferenc
On Monday, September 29th, 2025 at 13:52, Zakelly Lan
wrote:
>
>
> +1 & thanks Gavor for volunteering
>
> Best,
> Zakelly
>
> On Mon, Sep 29, 2025 at 7:30 PM Gyula Fora gyf...@apache.org wrote:
>
> > +1, and thanks Gabor for volunteering for this.
>
Ferenc Csaky created FLINK-38448:
Summary: Fix doc CI rsync logic
Key: FLINK-38448
URL: https://issues.apache.org/jira/browse/FLINK-38448
Project: Flink
Issue Type: Improvement
I meant 5 approving votes, 3 of which are binding. :)
On Friday, September 26th, 2025 at 12:07, Ferenc Csaky
wrote:
>
>
> Hello devs,
>
> I'm happy to announce that we have unanimously approved this release.
>
> There are 3 approving votes, 3 of which are bind
Hello devs,
I'm happy to announce that we have unanimously approved this release.
There are 3 approving votes, 3 of which are binding:
- Mate Czagany (non-binding)
- Gabor Somogyi (non-binding)
- Gyula Fóra (binding)
- Maximilian Michels (binding)
- Márton Balassi (binding)
There are no disapp
> > > > Hi,
> > > > >
> > > > > +1 (non-binding) - thanks for driving this release Ferenc!
> > > > >
> > > > > - Verified hashes and signatures
> > > > > - Built from source and tests passed
> > > > > -
Hi Mate,
Thanks for starting this discussion. Not really an expert on the topic, but
AFAIK build and distribute on its own will not have any effect, cause right
now, `flink-shaded-netty-tcnative-dynamic` [1] is put into the `opt` folder of
the Flink build, so until we do not change the assembly th
gt; > > Cheers
> > > Gyula
> > >
> > > On Thu, Sep 18, 2025 at 3:54 PM Maximilian Michels m...@apache.org
> > > wrote:
> > >
> > > > Thank you so much for creating the release! Unfortunately, I've just
> > > > f
Hi everyone,
Please review and vote on the release candidate #1 for the version 1.13.0 of
Apache Flink Kubernetes Operator,
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
Hi Gyula!
I agree that this would be nice to release as 1.13.0
I volunteer to be the release manager. I can also help to
merge/wrap-up the incomplete tasks.
Best,
Ferenc
On Monday, September 15th, 2025 at 15:18, Gyula Fóra
wrote:
>
>
> Hi Flink Devs!
>
> A couple months has passed sinc
+1 (binding)
Best,
Ferenc
On Tuesday, September 16th, 2025 at 14:23, Zakelly Lan
wrote:
>
>
> +1 (binding)
>
>
> Best,
> Zakelly
>
> On Tue, Sep 16, 2025 at 7:57 PM Ramin Gharib rgha...@confluent.io.invalid
>
> wrote:
>
> > +1 (non-binding)
> >
> > Cheers,
> >
> > Ramin
> >
> > On
eck the 5 uncompleted "2.1.0" tickets [1].
> >
> > 1.
> >
> > https://issues.apache.org/jira/issues/?jql=project %3D FLINK AND fixVersion
> > %3D 2.1.0 AND statusCategory %3D new
> >
> > Best,
> > Lincoln Lee
> >
> >
+1 and thanks for volunteering!
Also +1 to include the fix mentioned by Zakelly.
Best,
Ferenc
On Thursday, September 11th, 2025 at 11:11, Xintong Song
wrote:
>
>
> +1
>
> Best,
>
> Xintong
>
>
>
> On Thu, Sep 11, 2025 at 4:50 PM Zakelly Lan zakelly@gmail.com wrote:
>
> > +1 & Th
Hi!
I noticed that the "2.1.0" release has not yet been closed in Apache Jira.
Furthermore,
there is also a "2.1" release that also has 19 issues. Both contains unresolved
ones too.
May I kindly ask to close the tickets that were completed and move the
remaining ones into
2.1.1? I think every
Hi Mate,
Thank you for opening the discussion regarding the HBase connector. I think
releasing a connector version for 1.20 (LTS) is reasonable, as the connector
int its current form pretty outdated, and with the HBase 2.6 version it should
not be problematic to move forward to Flink 2.x in an upc
+1 (binding)
Best,
Ferenc
On Thursday, July 31st, 2025 at 14:32, Shengkai Fang wrote:
>
>
> +1(binding)
>
> Best,
> Shengkai
>
> Hao Li h...@confluent.io.invalid 于2025年7月30日周三 23:29写道：
>
> > Hi everyone,
> >
> > I'd like to start a vote on FLIP-529: Connections in Flink SQL and TableAPI
> > > (dependency-reduced-pom.xml) with unapproved licenses were found,
> > > > this should be fixed.
> > > >
> > > > Best,
> > > > Lincoln Lee
> > > >
> > > > Ron Liu ron9@gmail.com 于2025年7月23日周三 12:11写道：
> > > >
>
Ferenc Csaky created FLINK-38091:
Summary: Update japicmp configuration post 1.20.2
Key: FLINK-38091
URL: https://issues.apache.org/jira/browse/FLINK-38091
Project: Flink
Issue Type
Ferenc Csaky created FLINK-38092:
Summary: Update japicmp configuration post 1.19.3
Key: FLINK-38092
URL: https://issues.apache.org/jira/browse/FLINK-38092
Project: Flink
Issue Type
The Apache Flink community is very happy to announce the release of Apache
Flink 1.20.2, which is the second bugfix 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
The Apache Flink community is very happy to announce the release of Apache
Flink 1.19.3, which is the third bugfix 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
Ferenc Csaky created FLINK-38085:
Summary: Use buildx for Docker image creation
Key: FLINK-38085
URL: https://issues.apache.org/jira/browse/FLINK-38085
Project: Flink
Issue Type: Improvement
Hello devs,
I am the release manager of the 1.19.3 and 1.20.2 core Flink releases. Happy to
both
RCs have been approved, and I would like to move on and publish the artifacts,
but as
these are my first core product releases I do not have PyPI access yet to
publish the
related Python artifacts.
I'm happy to announce that we have unanimously approved this release.
There are 4 approving votes, 3 of which are binding:
- Mate Czagany (non-binding)
- Márton Balassi (binding)
- Sergey Nuyanzin (binding)
- Robert Metzger (binding)
There are no disapproving votes.
Thanks everyone!
I'm happy to announce that we have unanimously approved this release.
There are 5 approving votes, 3 of which are binding:
- Mate Czagany (non-binding)
- Márton Balassi (binding)
- Weiqing Yang (non-binding)
- Sergey Nuyanzin (binding)
- Zakelly Lan (binding)
There are no disapproving votes.
Th
-web PR
> > > >
> > > > Marton
> > > >
> > > > On Thu, Jun 19, 2025 at 7:28 PM Mate Czagany czmat...@gmail.com
> > > > wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > +1 (non-b
gt; > +1 (non-binding)
> > > >
> > > > - Reviewed release notes
> > > > - Verified checksums and signatures
> > > > - Verified that no binaries can be found in the source archives
> > > > - Verified that source can be built with Mav
+1 (binding)
Best,
Ferenc
On Thursday, June 19th, 2025 at 10:11, Gyula Fóra wrote:
>
>
> +1 (binding)
>
> Gyula
>
> On Mon, Jun 16, 2025 at 3:03 PM Etienne Chauchot echauc...@apache.org
>
> wrote:
>
> > Hi all,
> >
> > thanks for the updates Poorvank,
> >
> > LGTM. It is just missing
+1 (binding)
There definitely seems to be interest in bringing this connector under the
Apache
umbrella, and I don't see any reason why we shouldn't.
Best,
Ferenc
On Friday, June 20th, 2025 at 15:53, Mark Nuttall wrote:
>
>
> +1 (non-binding)
>
> On 2025/06/06 16:09:03 David Radley wrote:
Hi everyone,
Please review and vote on the release candidate #2 for the version 1.20.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],
Hi everyone,
Please review and vote on the release candidate #2 for the version 1.19.3, as
follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
The complete staging area is available for your review, which includes:
* JIRA release notes [1],
Ferenc Csaky created FLINK-37952:
Summary: Do not tar python wheel packages in GH Nightly workflow
Key: FLINK-37952
URL: https://issues.apache.org/jira/browse/FLINK-37952
Project: Flink
Since the tar archives are corrupt because of the usage of bsdtar, I close this
thread
and create a new RC and will post a new vote thread for that.
Thanks,
Ferenc
On Friday, May 30th, 2025 at 20:00, Ferenc Csaky
wrote:
>
>
> Hi everyone,
>
> Please review and vote
Since the tar archives are corrupt because of the usage of bsdtar, I close this
thread
and create a new RC and will post a new vote thread for that.
Thanks,
Ferenc
On Tuesday, June 10th, 2025 at 17:50, Ferenc Csaky
wrote:
>
>
> I think the same issue just came up in a rec
"._")
> cat shows that every files starts with "Mac OS X"
> I tend to think the reason is that probably for archives there were
> used some Mac specific tools which lead to problems in Linux
>
> On Sun, Jun 8, 2025 at 9:16 AM Ferenc Csaky ferenc.cs...@pm.me
I would like to highlight that, now the Azure pipeline is fixed,
there was a green CI run for the release-1.19 branch [1].
Best,
Ferenc
[1]
https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=68012&view=results
On Monday, June 2nd, 2025 at 17:36, Ferenc Csaky
w
+1 (binding)
Looking forward to this!
Best,
Ferenc
On Tuesday, June 3rd, 2025 at 11:32, David Radley
wrote:
>
>
> +1 non-binding.
> This is a very interesting area for us to add value.
>
> Warm regards, David.
>
> From: flin...@126.com flin...@126.com on behalf of Yuepeng Pan
> panyuep.
am not saying we should move forward, the GH CI is still
in beta, so we should definitely fix the Azure CI and get a green run,
but we should not drop RC1 yet.
Best,
Ferenc
[1] https://github.com/apache/flink/actions/runs/15382501322
[2] https://github.com/ferenc-csaky/flink/actions/runs
25?
> >
> > Not sure if it might block the release...
> >
> > [1] https://dev.azure.com/apache-flink/apache-flink/_build?definitionId=1
> >
> > Best regards,
> > Sergey
> >
> > On Fri, May 30, 2025, 13:29 Ferenc Csaky ferenc.cs...@pm.me.invalid w
Hi everyone,
Please review and vote on the release candidate #1 for the version 1.20.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],
Hi everyone,
Please review and vote on the release candidate #1 for the version 1.19.3, as
follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)
The complete staging area is available for your review, which includes:
* JIRA release notes [1],
> is very old (CentOS 5 (2007)) and deprecated
> > I would vote one migration but it would require quite some testing.
> > * Do I understand correctly that all wheels are intended to be built such a
> > way or just part of it?
> >
> > BR,
> > G
> >
for building wheel files,
cause it a lot simpler, and does not depend on anything other than GitHub.
WDYT?
Best,
Ferenc
[1]
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=73631092#CreatingaFlinkRelease-BuildandstageJavaandPythonartifacts
[2]
https://github.com/ferenc-csaky
Solid +1 for dropping instead of deprecate.
Best,
Ferenc
On Wednesday, May 28th, 2025 at 07:12, Gabor Somogyi
wrote:
>
>
> Hi Mika,
>
> +1 to drop and not just deprecate from my side.
>
> BR,
> G
>
>
> On Wed, May 28, 2025 at 7:06 AM Dian Fu dian0511...@gmail.com wrote:
>
> > Hi Mika,
Hi,
What branch and JDK version are you using? Is should not be necessary to
configure
`--add-opens` by hand. In the past, I ran into problems like this, when I was
moving back
and forth between JDK versions, and sometimes the IDE can stuck in a confused
state.
In general, I would suggest to i
Ferenc Csaky created FLINK-37820:
Summary: AsyncScalarFunction UDFs cannot be loaded via CompiledPlan
Key: FLINK-37820
URL: https://issues.apache.org/jira/browse/FLINK-37820
Project: Flink
Hello devs,
I would like to start a discussion about the next patch release for 1.19.
The 1.19.2 version was released almost 3 months ago, and although we do not
have tons of commits since then, I think the Parquet CVE fix would be good
to be released ASAP [1].
If there are no objections to the r
Hello devs,
I would like to start a discussion about the next patch release for 1.20.
The 1.20.1 version was released almost 3 months ago, and there are several
fixes since then, some of them mitigates security vulnerabilities [1].
If there are no objections to the release, I would like to volunt
Hi G,
Thanks for starting the discussion! The delivered items, the given timeline,
and the release cadence (1.11 released early March) makes sense to me.
+1 for the release and release manager.
Thanks,
Ferenc
On Thursday, May 8th, 2025 at 09:19, Gabor Somogyi
wrote:
>
>
> Hi All!
>
> I
+1 (binding)
Thanks for driving this!
Best,
Ferenc
On Tuesday, May 6th, 2025 at 14:50, Sergey Nuyanzin wrote:
>
>
> Thank you for driving this
> +1 (binding)
>
> On Tue, May 6, 2025, 12:04 Timo Walther twal...@apache.org wrote:
>
> > Hi everyone,
> >
> > I'd like to start a vote on FLI
Hi,
I think the FLIP is in a fairly good state, +1 for the idea and the given
design. This may be considered already, but IMO we should also add some
high-level details, pros, and cons of enabling this feature to the website
other than the config option description.
Best,
Ferenc
On Friday, Ma
Hi Mayank,
Thank you for starting the discussion! In general, I think such functionality
would be a really great addition to Flink.
Could you pls. elaborate a bit more one what is the reason of defining a
`connection` resource on the database level instead of the catalog level?
If I think about `
+1 (non-binding)
- verified signature and hashes
- checked no binaries in source release
- checked staging repository
- reviewed Jira release notes
- verified GH tag
- reviewed web PR
Thanks,
Ferenc
On Thursday, May 1st, 2025 at 04:38, Xiqian YU wrote:
>
>
> Thanks Kunni for preparing this
+1 (binding)
Thanks for driving this!
Best,
Ferenc
On Tuesday, April 29th, 2025 at 10:40, David Radley
wrote:
>
>
> As below – starting a new vote thread (thanks @Robert
> Metzgermailto:rmetz...@apache.org).
>
>
> I'd like to start a vote for FLIP-518: Introduce a community review
> p
+1 (binding)
Thanks for driving this!
On Friday, April 18th, 2025 at 16:57, Robert Metzger
wrote:
>
>
> +1 (binding)
>
> On Wed, Apr 16, 2025 at 10:39 AM Daren Wong darenwkt@gmail.com wrote:
>
> > Hi devs,
> >
> > Thank you everyone for the feedback on FLIP-524: CloudWatch Metric Sin
Glad to see this release happening!
+1 (non-binding)
- verified signatures and hashes
- checked no binaries in source release
- built from source with JDK11 & Maven 3.8.6
- verified artifacts in staging repo
- checked release notes
- verified GH tag and CI
- reviewed web PR
On Friday, April 18t
Ferenc Csaky created FLINK-37690:
Summary: Fix flaky Kudu test table datagen
Key: FLINK-37690
URL: https://issues.apache.org/jira/browse/FLINK-37690
Project: Flink
Issue Type: Technical Debt
The Apache Flink community is very happy to announce the release of Apache
flink-connector-kudu 2.0.0.
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
Ferenc Csaky created FLINK-37664:
Summary: Intergra Kudu connector docs
Key: FLINK-37664
URL: https://issues.apache.org/jira/browse/FLINK-37664
Project: Flink
Issue Type: New Feature
Hi everyone,
I am happy to announce that we have unanimously approved
this release.
There are 6 approving votes, 3 of which are binding:
- Gyula Fora (binding)
- Zakelly Lan (binding)
- Mate Czagany (non-binding)
- Xiqian Yu (non-binding)
- Yanquan Lv (non-binding)
- Marton Balassi (binding)
Th
ecked:
> > - Review JIRA release notes
> > - Verify hashes and verify signatures
> > - Build success from source with JDK11 & maven3.8.6
> > - Source code artifacts matching the current release
> > - Read the announcement blog and LGTM
> >
> > Ferenc Csaky feren
+1 (non-binding)
- verified checksum and signature
- checked no binaries in the source archive
- built source with JDK11 + Maven 3.8.6
- verified release tag, CI, and staging repo
- reviewed web PR
Best,
Ferenc
On Wednesday, April 9th, 2025 at 12:25, Xiqian YU wrote:
>
>
> +1 (non-binding)
+1 for the release and the release manager.
Thanks for driving this.
Best,
Ferenc
On Tuesday, April 8th, 2025 at 05:06, Leonard Xu wrote:
>
>
> +1, thanks @Arvid for driving this release!
>
> Best,
> Leonard
>
> > 2025 4月 7 18:02，Tom Cooper c...@tomcooper.dev 写道：
> >
> > +1 from me. Than
Congrats, Sergey!
Best,
Ferenc
On Monday, April 7th, 2025 at 03:30, weijie guo
wrote:
>
>
> Congratulations, Sergey~
>
> Best regards,
>
> Weijie
>
>
> Lincoln Lee lincoln.8...@gmail.com 于2025年4月3日周四 18:14写道：
>
> > Congratulations, Sergey!
> >
> > Best,
> > Lincoln Lee
> >
> > Yuepen
+1 (binding)
Best,
Ferenc
On Monday, March 31st, 2025 at 13:06, Rui Fan <1996fan...@gmail.com> wrote:
>
>
> +1(binding)
>
> Best,
> Rui
>
> On Mon, Mar 31, 2025 at 5:42 PM Andrei Kaigorodov <
> andreykaygoro...@gmail.com> wrote:
>
> > +1 (non-binding)
> >
> > Best regards,
> >
> > Andr
AFAIK the standard YAML config possibility were introduced in
Flink 1.19, it just coexisted with the old solution to keep bw
compatibility in the 1.x line.
If we bp it to 1.20, it's not much overhead to move it over to
1.19 as well I guess.
WDYT?
On Wednesday, April 2nd, 2025 at 17:23, Gabor S
Congratulations!
Best,
Ferenc
On Tuesday, April 1st, 2025 at 11:59, yue ma wrote:
>
>
> Congratulation, Zakelly!
>
> Junrui Lee jrlee@gmail.com 于2025年4月1日周二 17:38写道：
>
> > Congratulation, Zakelly!
> >
> > Best,
> > Junrui
> >
> > Leonard Xu xbjt...@gmail.com 于2025年4月1日周二 17:22写道：
>
Hi Tom,
Big +1 for this. On a slightly different note, do we know why the
CI run is still in beta? I see that it currently fails because of
Python problems, but AFAIK it was not really touched for quite some
time.
Is it just needs some more development time, or we have resource
limitations, maybe
Hi everyone,
Please review and vote on release candidate #1 for
flink-connector-kudu v2.0.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
By starting the release process I meant the steps to create
a RC, but the wording was confusing.
On Tuesday, March 25th, 2025 at 12:09, Ferenc Csaky
wrote:
>
>
> Thank you all for the inputs! If no objections until then,
> I will start the release process in Thursday (03-27).
rt Flink 1.19 and 1.20 (maybe 2.0 soon) and
> > > thanks for volunteering as the release manager.
> > >
> > > Cheers,
> > > Marton
> > >
> > > On Fri, Mar 21, 2025 at 1:00 PM Ferenc Csaky > >
> > > wrote:
> > >
> >
+1 (binding)
Thanks,
Ferenc
On Friday, March 21st, 2025 at 14:48, Őrhidi Mátyás
wrote:
>
>
> +1 (binding)
>
> On Thu, Mar 20, 2025 at 12:22 AM Gyula Fóra gyf...@apache.org wrote:
>
> > +1 (binding)
> >
> > And a gentle reminder to please vote :)
> >
> > Cheers,
> > Gyula
> >
> > On T
Hello devs,
I would like to start a discussion to release the externalized Kudu connector.
To make anyone
up to date regarding what happened until now and why, let me summarize the
story.
Originally, the Kudu connector was part of the Bahir Flink [1] repository, but
it was moved into
the attic
Ferenc Csaky created FLINK-37527:
Summary: Add `KuduSource` documentation
Key: FLINK-37527
URL: https://issues.apache.org/jira/browse/FLINK-37527
Project: Flink
Issue Type: New Feature
+1 (non-binding)
- Verified signatures and checksums
- Checked GH release tag
- Built src with JDK21 and Maven 3.8.6
- Deployed TopSpeedWindowing example to standalone cluster
- Ran dummy datagen SELECT via SQL client on standalone cluster
- Checked web PR that has quite some comments from David,
+1 (non-binding)
- Verified checksums and signatures
- Built source with JDK8 and Maven 3.8.6
- Reviewed web PR
Thanks,
Ferenc
On Tuesday, March 11th, 2025 at 09:17, Robert Metzger
wrote:
>
>
> +1 (binding)
>
> - Source archive looks ok (no binaries, maven builds, versions in pom seem
>
Ferenc Csaky created FLINK-37394:
Summary: Update CI Flink versions to 1.19 and 1.20 in Kudu
connector
Key: FLINK-37394
URL: https://issues.apache.org/jira/browse/FLINK-37394
Project: Flink
Ferenc Csaky created FLINK-37389:
Summary: Add "flink-sql-connector-kudu" module
Key: FLINK-37389
URL: https://issues.apache.org/jira/browse/FLINK-37389
Project: Flink
Issue Type
Hi,
Thanks for starting this discussion. +1 for the proposal and Timo's
addendum regarding the deprecation warning.
Best,
Ferenc
On Thursday, February 20th, 2025 at 11:30, Timo Walther
wrote:
>
>
> Hi Mika,
>
> thanks for bringing this up! I was actually quite surprised that we
> don't us
Ferenc Csaky created FLINK-37364:
Summary: Bump Flink 1.19, 1.20 patch versions in Flink CDC
Key: FLINK-37364
URL: https://issues.apache.org/jira/browse/FLINK-37364
Project: Flink
Issue Type
Congrats to everyone involved!
Thanks Alex for managing the release!
Best,
Ferenc
On Wednesday, February 19th, 2025 at 15:56, Alexander Fedulov
wrote:
>
>
> I would also like to explicitly thank Ferenc Csaky, Sergey Nuyanzin,
> Matthias Pohl, Marton Balassi, Max Michels, and
Congrats to everyone involved!
Thanks Alex for managing the release!
Best,
Ferenc
On Wednesday, February 19th, 2025 at 15:59, Alexander Fedulov
wrote:
>
>
> I would also like to explicitly thank Ferenc Csaky, Sergey Nuyanzin,
> Matthias Pohl, Marton Balassi, Max Michels, and
Hi,
according to a past discussion [1] at the end of January 2025, the
1.18 CI pipeline got disabled, so there is no plan to release
1.18.2.
Best,
Ferenc
[1] https://lists.apache.org/thread/5onl01vt98452vyj4x6flvdq8601fdo7
On Friday, February 14th, 2025 at 11:05, Yang LI
wrote:
>
>
> Dear
+1 (non-binding)
- verified signatures
- verified hashsums
- checked GH release tag
- checked no binaries in source archives
- built the source with jdk8 and maven 3.8.6
- reviewed web PR
- deployed WordCount job to local cluster
Thanks,
Ferenc
On Friday, January 31st, 2025 at 00:39, Yanquan
+1 for the proposal and the given timeline, really looking forward
to see 2.0 support in the operator.
Best,
Ferenc
On Friday, January 31st, 2025 at 10:27, Gyula Fóra wrote:
>
>
> Hi All!
>
> I would like to kick off the release planning for the 1.11 operator release.
>
> I think the cod
+1 (non-binfing)
- verified signatures
- verified hashsums
- checked GH release tag
- checked no binaries in source archives
- built the source with jdk8 and maven 3.8.6
- reviewed web PR
- deployed WordCount job to local cluster
Thanks,
Ferenc
On Thursday, January 30th, 2025 at 03:22, Yanqua
Ferenc Csaky created FLINK-37237:
Summary: Enforce SQL PRIMARY KEY definition for Kudu tables and
remove table option
Key: FLINK-37237
URL: https://issues.apache.org/jira/browse/FLINK-37237
Project
Ferenc Csaky created FLINK-37230:
Summary: Consolidate Kudu connector table options
Key: FLINK-37230
URL: https://issues.apache.org/jira/browse/FLINK-37230
Project: Flink
Issue Type
+1, looking forward to these changes!
Best,
Ferenc
On Wednesday, January 22nd, 2025 at 10:56, Leonard Xu wrote:
>
>
> +1 for the proposed code freeze date
>
> Best,
> Leonard
>
> > 2025年1月22日 15:41，ConradJam jam.gz...@gmail.com 写道：
> >
> > +1
> >
> > Yanquan Lv decq12y...@gmail.com 于20
nd wait for a new Pekko release that
> > > allows isolated Netty settings solely for flink-rpc:
> > > Pros:
> > > - Resolves the CVEs
> > > - Memory usage similar to Netty 3, reducing the risk of OOM surprises
> > > for users
> > > Cons:
> > >
Ferenc Csaky created FLINK-37190:
Summary: Make Kudu `FlushMode` configurable in Flink SQL
Key: FLINK-37190
URL: https://issues.apache.org/jira/browse/FLINK-37190
Project: Flink
Issue Type
ke time for the new Pekko release
>
> [1] https://github.com/apache/pekko/pull/1709#issuecomment-2599698240
>
> Unless we can hope for a timely Pekko release, my vote would be to go ahead
> with option 2 and clearly document the potential need for increasing
> container memory limit
Since `flink-runtime` uses Netty4 for quite a while, I believe
enforcing UNPOOLED will affect shuffle performance. I did not
performed actual tests comparing Netty3 and Netty4 in this regard,
so I cannot back this with actual numbers, but I think losing
shuffle performance would affect more real-wo
Thanks for the summary Alex!
+1 to keep Netty4.
Best,
Ferenc
On Thursday, January 16th, 2025 at 17:02, Tom Cooper wrote:
>
>
> + 1 on keeping the upgraded Pekko for 1.20.1.
>
> From what I could see, the only issues occurred in a end-to-end test that set
> the available memory to 7MB.
>
Ferenc Csaky created FLINK-37152:
Summary: Update Flink version to 1.20 in Flink CDC
Key: FLINK-37152
URL: https://issues.apache.org/jira/browse/FLINK-37152
Project: Flink
Issue Type
+1 (binding)
Looking forward to this!
Best,
Ferenc
On Friday, January 10th, 2025 at 12:28, Márton Balassi
wrote:
>
>
> +1 (binding)
>
> Thanks, G.
>
> On Thu, Jan 9, 2025 at 4:17 PM Zakelly Lan zakelly@gmail.com wrote:
>
> > +1 (binding)
> >
> > Thanks for driving this.
> >
> >
Ferenc Csaky created FLINK-37100:
Summary: Fix test_netty_shuffle_memory_control.sh in CI for JDK11+
Key: FLINK-37100
URL: https://issues.apache.org/jira/browse/FLINK-37100
Project: Flink
Ferenc Csaky created FLINK-37099:
Summary: Document possible Netty4 configurations to setup Pekko
properly in JDK11+
Key: FLINK-37099
URL: https://issues.apache.org/jira/browse/FLINK-37099
Project
Hi,
I spent some time on this issue and gathered my findings here [1].
ConradJam, if you have some time, can you mayve try to run your job
with the following dynamic params added to
`env.java.opts.taskmanager` in `config.yaml`:
-Dorg.apache.flink.shaded.netty4.io.netty.tryReflectionSetAccessib
Ferenc Csaky created FLINK-36855:
Summary: Implement Source API in Kudu connector
Key: FLINK-36855
URL: https://issues.apache.org/jira/browse/FLINK-36855
Project: Flink
Issue Type: New
Ferenc Csaky created FLINK-36839:
Summary: Update Kudu version to 1.17.1
Key: FLINK-36839
URL: https://issues.apache.org/jira/browse/FLINK-36839
Project: Flink
Issue Type: Improvement
1 - 100 of 237 matches
Mail list logo
