[
https://issues.apache.org/jira/browse/FLINK-6031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16015646#comment-16015646
]
Robert Metzger commented on FLINK-6031:
---------------------------------------
Merged for master (1.4) in
http://git-wip-us.apache.org/repos/asf/flink/commit/4a314a80
Merged for 1.3 in: http://git-wip-us.apache.org/repos/asf/flink/commit/ca3e403e
> Add parameter for per job yarn clusters to control whether the user code jar
> is included into the system classloader.
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-6031
> URL: https://issues.apache.org/jira/browse/FLINK-6031
> Project: Flink
> Issue Type: Bug
> Components: YARN
> Reporter: Robert Metzger
> Assignee: Chesnay Schepler
> Priority: Critical
> Fix For: 1.3.0, 1.4.0
>
>
> FLINK-4913 added the user jar into the system classloader, when starting a
> Flink per job YARN cluster.
> Some users were experiencing issues with the changed behavior.
> I suggest to introduce a new yarn specific configuration parameter (for the
> flink-conf.yaml file) to control if the user jar is added into system
> classloader.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
