You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Robert Metzger (Jira)" <ji...@apache.org> on 2020/08/24 17:45:00 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 ]

Robert Metzger updated FLINK-18742:
-----------------------------------
    Fix Version/s:     (was: 1.11.2)

> 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
>            Assignee: Matt Wang
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.12.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)