flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kostas Kloudas (Jira)" <j...@apache.org>
Subject [jira] [Issue Comment Deleted] (FLINK-14808) ClientUtils set thread ClassLoader that is different from the user cl of PackagedProgram
Date Fri, 15 Nov 2019 11:48:00 GMT

     [ https://issues.apache.org/jira/browse/FLINK-14808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kostas Kloudas updated FLINK-14808:
-----------------------------------
    Comment: was deleted

(was: I will open a PR with just the fix so that we have green builds and I will add a subtask
to create a test that will allow for this to not happen again.)

> 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
>            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)

Mime
View raw message