zentol commented on PR #20003: URL: https://github.com/apache/flink/pull/20003#issuecomment-1162750463
I'm pretty sure you are correct. We never actually had the case where we had a tree of classloaders with different order settings between nodes. It's always been either all child-first or all parent-first. We'd have to change directions several times (from a call to the child CL, go up to default jars and try loading the class, _then_ drill down to other user jars and try loading the class, then jump up to the Flink CL and try loading the class). That's just not supported. (And really we shouldn't because good look wrapping your head around that). So let's discard _that_ idea. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
