This is expected behavior. Since jar A is on the classpath you are able
to access the entry-class of said jar. When you specify the jar id all
that does is put another jar on the classpath; it is not enforce that
the entry-class is loaded from said jar.
On 08/01/2022 16:45, Qihua Yang wrote:
Hi Yun,
Thank you for your reply! testB.jar doesn't have the same entry class as
testA.jar.
So is it expected behavior? What is the theory behind?
Thanks,
Qihua
On Fri, Jan 7, 2022 at 4:27 PM Yun Gao wrote:
>
> Hi Qihua
>
> Sorry may I double confirm that whether the entry class exists in both
Hi Qihua
Sorry may I double confirm that whether the entry class exists in both testA
and testB?
IF testA.jar is included on startup, it would be loaded in the parent
classloader, which
is the parent classloader for the user classloader that loads testB. Thus at
least if the
entry-class is ex
Hi,
I found a weird behavior. We launched a k8s cluster without job. But
includes the jar A. I use Flink rest api to upload a dummy jar(actually it
can be any jar). Flink will create a jar id. Then I use rest api to start
the job with the jar A entry-class. But the jar id is the dummy jar id.
Flin
