[ANNOUNCE] Apache Flink 1.19.3 released

2025-07-11 Thread Ferenc Csaky
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

[ANNOUNCE] Apache Flink 1.20.2 released

2025-07-11 Thread Ferenc Csaky
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

[ANNOUNCE] Apache Flink Kubernetes Operator 1.12.1 released

2025-07-11 Thread Gyula Fóra
The Apache Flink community is very happy to announce the release of Apache Flink Kubernetes Operator 1.12.1. The Flink Kubernetes Operator allows users to manage their Apache Flink applications and their lifecycle through native k8s tooling like kubectl. The release is available for download at:

[jira] [Created] (FLINK-38090) TableResult.collect() returns incorrect SQL inline structured types

2025-07-11 Thread Timo Walther (Jira)
Timo Walther created FLINK-38090: Summary: TableResult.collect() returns incorrect SQL inline structured types Key: FLINK-38090 URL: https://issues.apache.org/jira/browse/FLINK-38090 Project: Flink

Re: [ANNOUNCE] Apache Flink 1.19.3 released

2025-07-11 Thread Sergey Nuyanzin
Congratulations to everyone involved! Thank you Ferenc for managing the release! On Fri, Jul 11, 2025 at 1:13 PM Ferenc Csaky wrote: > > 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

Re: [ANNOUNCE] Apache Flink 1.20.2 released

2025-07-11 Thread Sergey Nuyanzin
Congratulations to everyone involved! Thank you Ferenc for managing the release! On Fri, Jul 11, 2025 at 1:15 PM Ferenc Csaky wrote: > > 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 > serie

[jira] [Created] (FLINK-38089) Avoid pushing down non-deterministic filter in agg, join and union

2025-07-11 Thread Qilong Wang (Jira)
Qilong Wang created FLINK-38089: --- Summary: Avoid pushing down non-deterministic filter in agg, join and union Key: FLINK-38089 URL: https://issues.apache.org/jira/browse/FLINK-38089 Project: Flink

RE: [RESULT][VOTE] Flip-532 Donate GetInData HTTP Connector to Flink

2025-07-11 Thread David Radley
Hello, @Robert Metzger thanks for creating the repo [1]. I have not yet populated it yet; I will spend time of this after my summer vacation. I wanted to raise a concern around the http connector. I am aware that there are many Flink connectors and only some of them

Flink HTTP connector health proposal going forward.

2025-07-11 Thread David Radley
Hello, Raising this as new thread -so it is more noticeable. I wanted to raise a concern around the http connector. I am aware that there are many Flink connectors and only some of them have released versions for Flink 1.20 and even less work with Flink 2.0. I do not want this to be the fate of

[jira] [Created] (FLINK-38091) Update japicmp configuration post 1.20.2

2025-07-11 Thread Ferenc Csaky (Jira)
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: Technica

[jira] [Created] (FLINK-38092) Update japicmp configuration post 1.19.3

2025-07-11 Thread Ferenc Csaky (Jira)
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: Technica

Re: Flink HTTP connector health proposal going forward.

2025-07-11 Thread Martijn Visser
Hi David, Thanks for bringing this up. I understand the concern that you're bringing forward, but I think that's not the right solution here. 1. When the FLIP was brought up and discussed, this should have been a discussion topic from the beginning. If there are no committers available to help sh