zentol commented on PR #20003: URL: https://github.com/apache/flink/pull/20003#issuecomment-1162721597
> If we force to use parent-first mode, then the classloader behavior is inconsistent between local job compiling and distributed. Say the user wants to use child-first for distributed execution to resolve class conflict between user jar and flink core jar. However, the job can't be compiled because the client forces to use parent-first and ignores users' classloader.resolve-order configuration and causes NoSuchMethod exceptions. Sorry if I had not made it clear, when I said child-first I only referred to the new child CLs. Flink CL <order_set_by_user> User CL <parent-first> child user CL 1 <parent-first> child user CL 2 -- 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
