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

Gary Yao commented on FLINK-11781:
----------------------------------

[~watters_fish] There is a codepath using {{UserJarInclusion.FIRST}} [1]. 
However, I have not tested whether this works correctly. Because 1.7 is not 
supported anymore, you may want to test the feature with a newer release, such 
as 1.8 or 1.9. If it still doesn't work, please create a new issue in jira.

[1] 
https://github.com/apache/flink/blob/release-1.7/flink-yarn/src/main/java/org/apache/flink/yarn/AbstractYarnClusterDescriptor.java#L826

> Reject "DISABLED" as value for yarn.per-job-cluster.include-user-jar
> --------------------------------------------------------------------
>
>                 Key: FLINK-11781
>                 URL: https://issues.apache.org/jira/browse/FLINK-11781
>             Project: Flink
>          Issue Type: Bug
>          Components: Deployment / YARN
>    Affects Versions: 1.6.4, 1.7.2, 1.8.0
>            Reporter: Gary Yao
>            Assignee: Gary Yao
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.8.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> *Description*
> Setting {{yarn.per-job-cluster.include-user-jar: DISABLED}} in 
> {{flink-conf.yaml}} is not supported (anymore). Doing so will lead to the job 
> jar not being on the system classpath, which is mandatory if Flink is 
> deployed in job mode. The job will never run.
> *Expected behavior*
> Documentation should reflect that setting 
> {{yarn.per-job-cluster.include-user-jar: DISABLED}} does not work.
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to