[
https://issues.apache.org/jira/browse/FLINK-18211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17136406#comment-17136406
]
Kostas Kloudas commented on FLINK-18211:
----------------------------------------
[~fly_in_gis] is right that the {{pipeline.jars}} was not designed for this
purpose. It simply made explicit the list of jars detected when creating the
{{PackagedProgram}}. So this makes me wonder how was the shipping done before.
The {{env.registerCachedFile}} is one way. Was there ever any other way apart
from the {{yarnship}} which is Yarn specific?
The {{pipeline.classpaths}} are not shipped but they are expected to be there
already.
> 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)
