[
https://issues.apache.org/jira/browse/FLINK-18211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17136336#comment-17136336
]
Yang Wang commented on FLINK-18211:
-----------------------------------
[~kkl0u] Is {{pipeline.jars}} designed to cover this use case? When the users
want to submit a Flink job to existing standalone/Yarn/K8s session, it could be
used to ship dependencies via Flink distributed cache(aka blob storage).
Currently, we could only do this via {{env.registerCachedFile}} in main code.
> 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)
