[
https://issues.apache.org/jira/browse/FLINK-18211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17141734#comment-17141734
]
Kostas Kloudas commented on FLINK-18211:
----------------------------------------
I understand the usefulness of such a feature, my only concern is that we
already have a lot of command-line options out there. What about allowing the
user to specify additional jars via the {{GenericCLI}} only, by adding them to
the {{pipeline.jars}}, and not adding more CLI options fro the
{{FlinkYarnSessionCli}} (as described in
https://issues.apache.org/jira/browse/FLINK-13837) ?
I understand that this will be inconsistent between the two CLIs, but 1) I
think this is a motivation for users to start moving towards the {{GenericCLI}}
and 2) this behaviour was not supported before so it is not a regression.
What do you think [~fly_in_gis] and @[~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)
