resulting
set of configs.
BTW, how does it work when using Kubernetes operator?
Nix
From: Nikola Milutinovic
Date: Tuesday, January 28, 2025 at 6:10 PM
To: user@flink.apache.org
Subject: Re: table.exec.source.idle-timeout support
Hi Zhao.
Yes, I am deploying our solution as a Session Cluster on
: table.exec.source.idle-timeout support
Hi,
Are you deploying the job in Session mode? Underneath, Flink distinguishes
cluster-level and job-level configs. For Application mode, the two are unified.
When a job is submitted to the session cluster though, the values of
cluster-level config options, such
,
Zhanghao Chen
From: Nikola Milutinovic
Sent: Friday, January 10, 2025 23:48
To: user@flink.apache.org
Subject: Re: table.exec.source.idle-timeout support
Hi Nic.
I do not have a solution (soy), but have seen something similar. And have
complained about it
: Friday, January 10, 2025 at 4:22 PM
To: user@flink.apache.org
Subject: table.exec.source.idle-timeout support
Hi, I’m deploying Flink 1.19 via the k8s operator.
I’m setting `table.exec.source.idle-timeout: 30 s` in the
`spec.flinkConfiguration` section of the FlinkDeployment CR.
The Flink UI
Hi, I’m deploying Flink 1.19 via the k8s operator.
I’m setting `table.exec.source.idle-timeout: 30 s` in the
`spec.flinkConfiguration` section of the FlinkDeployment CR.
The Flink UI is showing the JobManager has been configured with the value and
the JM and TM logs both show `INFO [] - Loading
