[ 
https://issues.apache.org/jira/browse/FLINK-18211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17138420#comment-17138420
 ] 

Kostas Kloudas edited comment on FLINK-18211 at 6/17/20, 1:14 PM:
------------------------------------------------------------------

Can we go a bit back to why the {{env.registerCachedFile}} is not enough? I can 
only find the disadvantage that in Application Mode the {{registerCachedFile}} 
cannot be used because the {{main()}} runs on the cluster. But this is the only 
case I can find. 

Also in the jira issue that you mentioned [~fly_in_gis] it seems that in the 
case of Yarn, the new options are redundant, right?


was (Author: kkl0u):
Can we go a bit back to why the {{env.registerCachedFile}} is not enough? I can 
only find the disadvantage that in Application Mode the registerCachedFile 
cannot be used. But this is the only case I can find. 

Also in the jira issue that you mentioned [~fly_in_gis] it seems that in the 
case of Yarn, the new options are redundant, right?

> 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)

Reply via email to