[
https://issues.apache.org/jira/browse/FLINK-14808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16975634#comment-16975634
]
Kostas Kloudas commented on FLINK-14808:
----------------------------------------
[~tison] could you also point me to the other JIRAs you found that are related
to this so that I can close them?
> ClientUtils set thread ClassLoader that is different from the user cl of
> PackagedProgram
> ----------------------------------------------------------------------------------------
>
> Key: FLINK-14808
> URL: https://issues.apache.org/jira/browse/FLINK-14808
> Project: Flink
> Issue Type: Bug
> Components: Client / Job Submission
> Affects Versions: 1.10.0
> Reporter: Jingsong Lee
> Assignee: Kostas Kloudas
> Priority: Blocker
> Fix For: 1.10.0
>
>
> In ClientUtils.executeProgram, it create a new userCodeClassLoader and set it
> to thread context. (Name it cl1).
> But in PackagedProgram, it use a different class loader to create user Class.
> (Name it cl2).
> So in user's code, if user use thread loader to create a class, this class
> is come from cl1, if user want to work this class with their own class, there
> should be a failure, because them come from different class loader.
> Root cause: https://issues.apache.org/jira/browse/FLINK-14745
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
