[
https://issues.apache.org/jira/browse/FLINK-7442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16131889#comment-16131889
]
ASF GitHub Bot commented on FLINK-7442:
---------------------------------------
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/4554
Ah, I see - that is probably related to reading resources from a jar file
(like the config), methods like `getResourceAsStream()`.
I can see that the "delegate to parent after child" lookup logic might not
quite work for that, yes.
I think that particular bug you encountered there is almost an argument to
not change the logic on the client, yet. Since we would run the entire Flink
code through that classloader as well, the implications are trickier than in
the runtime task, where we only instantiate the user code functions.
> Add option for using a child-first classloader for loading user code
> --------------------------------------------------------------------
>
> Key: FLINK-7442
> URL: https://issues.apache.org/jira/browse/FLINK-7442
> Project: Flink
> Issue Type: Improvement
> Components: Local Runtime
> Reporter: Aljoscha Krettek
> Assignee: Aljoscha Krettek
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
