Hao Li created FLINK-38067:
--
Summary: Release Testing: Verify FLIP-525: Model ML_PREDICT,
ML_EVALUATE Implementation Design
Key: FLINK-38067
URL: https://issues.apache.org/jira/browse/FLINK-38067
Project: Fl
Hao Li created FLINK-38068:
--
Summary: Fix distribution
Key: FLINK-38068
URL: https://issues.apache.org/jira/browse/FLINK-38068
Project: Flink
Issue Type: Sub-task
Reporter: Hao Li
Dylan He created FLINK-38069:
Summary: The nullability of function ENCODE return type differs in
Table API and SQL
Key: FLINK-38069
URL: https://issues.apache.org/jira/browse/FLINK-38069
Project: Flink
Yash Anand created FLINK-38070:
--
Summary: Release Testing: Verify FLIP-507 : Add Model DDL methods
in TABLE API
Key: FLINK-38070
URL: https://issues.apache.org/jira/browse/FLINK-38070
Project: Flink
Hi all,
I’d like to initiate a discussion about adding UDF metrics.
*Motivation*
User-defined functions (UDFs) are essential for custom logic in Flink jobs
but often act as black boxes, making debugging and performance tuning
difficult. When issues like high latency or frequent exceptions occur,
Weiqing Yang created FLINK-38071:
Summary: FLIP-485: Add UDF Metrics
Key: FLINK-38071
URL: https://issues.apache.org/jira/browse/FLINK-38071
Project: Flink
Issue Type: New Feature
C
Siddharth R created FLINK-38064:
---
Summary: Bump cyclonedx-maven-plugin from 2.7.7 to 2.9.1
Key: FLINK-38064
URL: https://issues.apache.org/jira/browse/FLINK-38064
Project: Flink
Issue Type: Imp
Hao Li created FLINK-38066:
--
Summary: Release Testing: Verify FLIP-437: Support ML Models in
Flink SQL
Key: FLINK-38066
URL: https://issues.apache.org/jira/browse/FLINK-38066
Project: Flink
Issue T
+1 on the overall proposal. I think these guidelines make sense for
reducing confusion and respecting contributors’ work.
One scenario I'd also like to discuss is when there's a discussion thread
with a proposal document but no FLIP created yet - so it's still in the
early discussion phase. In pra
potterhe created FLINK-38061:
Summary: Caused by: java.util.ConcurrentModificationException When
the MySql Chunk Split stage triggers a checkpoint
Key: FLINK-38061
URL: https://issues.apache.org/jira/browse/FLINK-3806
+1 (binding)
Verified:
- Sources & signatures
- Installed operator and ran example applications and session jobs,
verified exception handling / events
- Built from source
Cheers,
Gyula
On Tue, Jul 8, 2025 at 10:07 AM Robert Metzger wrote:
> ok, thanks a lot. So my +1 on the RC makes sense ;
Sergey Nuyanzin created FLINK-38062:
---
Summary: ENCODE behaves wrong
Key: FLINK-38062
URL: https://issues.apache.org/jira/browse/FLINK-38062
Project: Flink
Issue Type: Technical Debt
@Robert Metzger :
The session clusters do not get too many events from the FKO (only things
like spec change etc) but most events are job related at the moment.
So this is expected, but could be improved :)
Gyula
On Tue, Jul 8, 2025 at 9:17 AM Robert Metzger wrote:
> +1 (binding)
>
> - I've su
ok, thanks a lot. So my +1 on the RC makes sense ;)
On Tue, Jul 8, 2025 at 10:03 AM Gyula Fóra wrote:
> @Robert Metzger :
> The session clusters do not get too many events from the FKO (only things
> like spec change etc) but most events are job related at the moment.
> So this is expected, bu
+1 (binding)
- I've successfully installed the operator RC
- launched a application mode job, exception events get reported properly
- launched a session cluster, submitted a job. *Neither exception events,
nor any other events (from FKO) get reported for the session cluster. Is
this expected?*
-
Hi,
I can see that the Flink operator uses the 6.13.2 Kubenetes client . We are
looking to move up to use 7.20 to pick up security fixes. I see
https://github.com/fabric8io/kubernetes-client/blob/main/doc/MIGRATION-v7.md.
Any thoughts on the impact and whether there is a community support for t
Hi David!
I think we should definitely pick up the latest version if possible, we
have to make sure that this is compatible with how Flink uses the client
for native integration though.
Cheers
Gyula
On Tue, Jul 8, 2025 at 6:02 PM David Radley wrote:
> Hi,
> I can see that the Flink operator us
Hi David,
I had a conversation in the dim distant past about doing this and I remember
that the the main issue with the upgrade in the operator was that the main
Flink repo [1] had not upgraded yet and that there could be conflicts? However,
I am drawing a blank on the exact details.
+1 for w
Thomas Cooper created FLINK-38063:
-
Summary: Update dependencies in the Flink Connector Kafka Project
Key: FLINK-38063
URL: https://issues.apache.org/jira/browse/FLINK-38063
Project: Flink
Is
Sergei Morozov created FLINK-38065:
--
Summary: Mismatching bracket in PostgresOffset#toString
Key: FLINK-38065
URL: https://issues.apache.org/jira/browse/FLINK-38065
Project: Flink
Issue Type
20 matches
Mail list logo
