[
https://issues.apache.org/jira/browse/FLINK-11781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17017652#comment-17017652
]
watters.wang commented on FLINK-11781:
--------------------------------------
[~gjy] hi, In Flink 1.7, does it support to specify
yarn.per-job-cluster.include-user-jar with "-yD
yarn.per-job-cluster.include-user-jar FIRST"?
I found that, "-yD yarn.tags' is effective, but "-yD
yarn.per-job-cluster.include-user-jar FIRST" isn't.
> 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)
