[ https://issues.apache.org/jira/browse/FLINK-18211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17141882#comment-17141882 ]
Kostas Kloudas commented on FLINK-18211: ---------------------------------------- I think that you are right [~fly_in_gis] that the {{pipeline.cached-files}} seems more appropriate for what we are discussing here. Essentially, the {{pipeline.cached-files}} seems like a non-programmatic replacement of the {{env.registerCachedFile}}. Also I agree that we should probably make the {{pipeline.jars}} internal. Does this solve your requirements [~Echo Lee]? > Dynamic properties setting 'pipeline.jars' will be overwritten > -------------------------------------------------------------- > > Key: FLINK-18211 > URL: https://issues.apache.org/jira/browse/FLINK-18211 > Project: Flink > Issue Type: Bug > Components: Client / Job Submission > Affects Versions: 1.10.0, 1.11.0 > Reporter: Echo Lee > Assignee: Echo Lee > Priority: Major > Labels: pull-request-available > Fix For: 1.12.0 > > > When we submit the application through "flink run > -Dpipeline.jars='/user1.jar, user2.jar'..." command, configuration will > include 'pipeline.jars', But ExecutionConfigAccessor#fromProgramOptions will > be reset this property, So the property set by the user is invalid. -- This message was sent by Atlassian Jira (v8.3.4#803005)