[
https://issues.apache.org/jira/browse/FLINK-39441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18089313#comment-18089313
]
Dennis-Mircea Ciupitu commented on FLINK-39441:
-----------------------------------------------
>From the operator side this looks correct.
>{{FlinkConfigBuilder.applyFlinkConfiguration}} copies every
>{{flinkConfiguration}} key verbatim into the effective cluster config, with no
>filtering of {{{}table.*{}}}, which matches your observation that the value
>reaches the configuration. So the operator is doing its job.
Whether a globally-set {{table.exec.*}} is then applied at runtime is Flink
Table API / core behavior, depending on how the SQL runner builds the
{{TableEnvironment}} (whether {{TableConfig}} is seeded from the cluster
config). That also explains why {{SET '...'}} works, and lines up with
[~au_miner] not being able to reproduce. So this is at most a Flink core /
Table issue, not an operator one. (cc [~gyfora])
> 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)
