[ 
https://issues.apache.org/jira/browse/FLINK-39441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nic Townsend updated FLINK-39441:
---------------------------------
    Description: 
https://nightlies.apache.org/flink/flink-docs-release-2.2/docs/dev/table/config/
 says:

{quote}Note: All of the following configuration options can also be set 
globally in Flink configuration file and can be later on overridden in the 
application, through EnvironmentSettings, before instantiating the 
TableEnvironment, or through the TableConfig of the TableEnvironment.{quote}

However, when I set {{table.exec.source.idle-timeout}} on a {{FlinkDeployment}} 
- it makes its way to the configuration but it doesn't take effect.

 !image-2026-04-15-14-42-31-175.png! 

I have use to use {[SET 'table.exec.source.idle-timeout' = '10s'}} inside my 
executed SQL or use {{scan.watermark.idle-timeout}}.

My usecase is that I have a containerised SQL runner application - it just runs 
the SQL that I supply. As such, I don't want to hard code values when creating 
{{TableEnvironment}} and I want to set it on the individual {{FlinkDeployment}} 
instead 

  was:
https://nightlies.apache.org/flink/flink-docs-release-2.2/docs/dev/table/config/
 says:

{quote}Note: All of the following configuration options can also be set 
globally in Flink configuration file and can be later on overridden in the 
application, through EnvironmentSettings, before instantiating the 
TableEnvironment, or through the TableConfig of the TableEnvironment.{quote}

However, when I set {{table.exec.source.idle-timeout}} on a {{FlinkDeployment}} 
- it makes its way to the configuration but it doesn't take effect.

 !image-2026-04-15-14-42-31-175.png! 

I have use to use [SET 'table.exec.source.idle-timeout' = '10s'} inside my 
executed SQL.

My usecase is that I have a containerised SQL runner application - it just runs 
the SQL that I supply. As such, I don't want to hard code values when creating 
{{TableEnvironment}} and I want to set it on the individual {{FlinkDeployment}} 
instead 


> Table configuration inside Flink config is not applying at runtime
> ------------------------------------------------------------------
>
>                 Key: FLINK-39441
>                 URL: https://issues.apache.org/jira/browse/FLINK-39441
>             Project: Flink
>          Issue Type: Bug
>          Components: Kubernetes Operator, Runtime / Configuration, Table SQL 
> / API
>    Affects Versions: 2.2.0
>         Environment: Flink Operator 1.13, Flink 2.2.0, RedHat Openshift 4.21.2
>            Reporter: Nic Townsend
>            Priority: Major
>         Attachments: image-2026-04-15-14-42-31-175.png, 
> image-2026-04-15-14-42-51-006.png
>
>
> https://nightlies.apache.org/flink/flink-docs-release-2.2/docs/dev/table/config/
>  says:
> {quote}Note: All of the following configuration options can also be set 
> globally in Flink configuration file and can be later on overridden in the 
> application, through EnvironmentSettings, before instantiating the 
> TableEnvironment, or through the TableConfig of the TableEnvironment.{quote}
> However, when I set {{table.exec.source.idle-timeout}} on a 
> {{FlinkDeployment}} - it makes its way to the configuration but it doesn't 
> take effect.
>  !image-2026-04-15-14-42-31-175.png! 
> I have use to use {[SET 'table.exec.source.idle-timeout' = '10s'}} inside my 
> executed SQL or use {{scan.watermark.idle-timeout}}.
> My usecase is that I have a containerised SQL runner application - it just 
> runs the SQL that I supply. As such, I don't want to hard code values when 
> creating {{TableEnvironment}} and I want to set it on the individual 
> {{FlinkDeployment}} instead 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to