[
https://issues.apache.org/jira/browse/FLINK-28213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17580685#comment-17580685
]
Zhu Zhu commented on FLINK-28213:
---------------------------------
I agree that we should not change the semantics of the {{PublicEvolving}}
method {{StreamExecutionEnvironment#configure()}}, from setting to merging.
Maybe we can add the user set {{PipelineOptions.JARS}} to
{{TableConfig.configuration}} on table environment initialization. Later the
table module can add new jars into {{PipelineOptions.JARS}} in
{{TableConfig.configuration}}. And finally the {{PipelineOptions.JARS}} in
{{TableConfig.configuration}} can just override that in the {{configuration}}
in {{StreamExecutionEnvironment}} via
{{StreamExecutionEnvironment#configure()}}.
This behavior can be explained as the table module is enriching/modifying the
user set {{PipelineOptions.JARS}} with program options or job configs, which I
think is acceptable, because it's already happening (e.g.
ExecutionConfigAccessor#fromProgramOptions(...)).
> StreamExecutionEnvironment configure method support override pipeline.jars
> option
> ---------------------------------------------------------------------------------
>
> Key: FLINK-28213
> URL: https://issues.apache.org/jira/browse/FLINK-28213
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Configuration
> Affects Versions: 1.16.0
> Reporter: dalongliu
> Assignee: dalongliu
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.16.0
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
