You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2021/06/08 22:43:03 UTC
[jira] [Updated] (FLINK-18742) Some configuration args do not take
effect at client
[ https://issues.apache.org/jira/browse/FLINK-18742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Flink Jira Bot updated FLINK-18742:
-----------------------------------
Labels: auto-deprioritized-major auto-unassigned pull-request-available (was: auto-unassigned pull-request-available stale-major)
Priority: Minor (was: Major)
This issue was labeled "stale-major" 7 ago and has not received any updates so it is being deprioritized. If this ticket is actually Major, please raise the priority and ask a committer to assign you the issue or revive the public discussion.
> Some configuration args do not take effect at client
> ----------------------------------------------------
>
> Key: FLINK-18742
> URL: https://issues.apache.org/jira/browse/FLINK-18742
> Project: Flink
> Issue Type: Improvement
> Components: Command Line Client
> Affects Versions: 1.11.1
> Reporter: Matt Wang
> Priority: Minor
> Labels: auto-deprioritized-major, auto-unassigned, pull-request-available
> Fix For: 1.14.0
>
>
> Some configuration args from command line will not work at client, for example, the job sets the {color:#505f79}_classloader.resolve-order_{color} to _{color:#505f79}parent-first,{color}_ it can work at TaskManager, but Client doesn't.
> The *FlinkUserCodeClassLoaders* will be created before calling the method of _{color:#505f79}getEffectiveConfiguration(){color}_ at {color:#505f79}org.apache.flink.client.cli.CliFrontend{color}, so the _{color:#505f79}Configuration{color}_ used by _{color:#505f79}PackagedProgram{color}_ does not include Configuration args.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)