Re: classloader.resolve-order is not honored when submitting job to a remote cluster

2021-06-01 Thread tao xiao
Hi Till, The PR covers the problem and it will fix the inconsistent class loading issue On Tue, Jun 1, 2021 at 9:55 PM Till Rohrmann wrote: > Hi Tao, > > I think this looks like a bug to me. Could it be that this problem is > covered by [1, 2]? Maybe you can review this PR and check whether it

Re: classloader.resolve-order is not honored when submitting job to a remote cluster

2021-06-01 Thread Till Rohrmann
Hi Tao, I think this looks like a bug to me. Could it be that this problem is covered by [1, 2]? Maybe you can review this PR and check whether it solves the problem. If yes, then let's quickly get it in. [1] https://issues.apache.org/jira/browse/FLINK-21445 [2] https://github.com/apache/flink/pu

classloader.resolve-order is not honored when submitting job to a remote cluster

2021-05-30 Thread tao xiao
Hi team, I discovered that child first class loader is always used to initialize the main program when submitting the job to a yarn cluster using application mode regardless of what value classloader.resolve-order is set in flink-conf.yaml. But this is not the case if I submit the same job with th