[
https://issues.apache.org/jira/browse/FLINK-13840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16920688#comment-16920688
]
Till Rohrmann commented on FLINK-13840:
---------------------------------------
Thanks for creating this document [~maguowei]. I took a look and added some
comments. I think the first version of it can be super simple. The only thing
we need to introduce is something like a {{Collection<URL>
getUserCodeClasspaths()}} method which we use to pass the user code classpaths
to the {{PackagedProgram}} in the {{ClassPathJobGraphRetriever}} or to create a
user code class loader with which to deserialize the {{JobGraph}} in the
{{FileJobGraphRetriever}}. There should not be the need to adapt any parts of
the CLI or other client classes for the MVP if I'm not mistaken.
> Let StandaloneJobClusterEntrypoint use user code class loader
> -------------------------------------------------------------
>
> Key: FLINK-13840
> URL: https://issues.apache.org/jira/browse/FLINK-13840
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Affects Versions: 1.9.0, 1.10.0
> Reporter: Till Rohrmann
> Priority: Major
> Fix For: 1.10.0
>
>
> In order to resolve class loading issues when using the
> {{StandaloneJobClusterEntryPoint}}, it would be better to run the user code
> in the user code class loader which supports child first class loading. At
> the moment, the user code jar is part of the system class path and, hence,
> part of the system class loader.
> An easy way to solve this problem would be to place the user code in a
> different directory than {{lib}} and then specify this path as an additional
> classpath when creating the {{PackagedProgram}}.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
