wuchong commented on PR #20003: URL: https://github.com/apache/flink/pull/20003#issuecomment-1162734430
This still seems inconsistent classloader behavior compared to the distributed execution. Please correct me if I'm wrong. When resolve-order is child-first, the classloader order in client is: `User CL` > `Flink CL` > `child user CL 1` > `child user CL 2` which means the jar find path is: default user jars > flink jars > user jar 1 > user jar 2 However, the classloader order (jar find path) in runtime is: default user jars > user jar 1 > user jar 2 > flink jars -- 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