You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Robert Metzger (Jira)" <ji...@apache.org> on 2019/12/12 13:31:00 UTC
[jira] [Commented] (FLINK-14893) Using Child ClassLoader to load
class when Parent ClassLoader couldn't load in ParentFirstPatterns
[ https://issues.apache.org/jira/browse/FLINK-14893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16994664#comment-16994664 ]
Robert Metzger commented on FLINK-14893:
----------------------------------------
I'm closing this ticket (see PR discussion)
> Using Child ClassLoader to load class when Parent ClassLoader couldn't load in ParentFirstPatterns
> ----------------------------------------------------------------------------------------------------
>
> Key: FLINK-14893
> URL: https://issues.apache.org/jira/browse/FLINK-14893
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Task
> Affects Versions: 1.9.0
> Reporter: hailong wang
> Assignee: hailong wang
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.11.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> In ChildFirstClassLoader#loadClass, when a class is in ParentFirstPattern, but it load failed for that parent does not contain it. It will throw a ClassNotFoundException. I think when loading failed, we should use findClass to load later.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)