Thanks Biao/Till, that answers my question.
On Tue, 18 Jun 2019 at 01:41, Till Rohrmann wrote:
> Hi Abdul,
>
> as Biao said the `--classpath` option should only be used if you want to
> make dependencies available which are not included in the submitted user
> code jar. E.g. if you have install
Hi Abdul,
as Biao said the `--classpath` option should only be used if you want to
make dependencies available which are not included in the submitted user
code jar. E.g. if you have installed a large library which is too costly to
ship every time you submit a job. Usually, you would not need to s
Ah, sorry for misunderstanding.
So what you are asking is that why we need "--classpath"? I'm not sure what
the original author think of it. I guess the listed below might be
considered.
1. Avoid duplicated deploying. If some common jars are deployed in advance
to each node of cluster, the jobs dep
Hi Biao,
I am aware of it - that's not my question.
On Mon, Jun 17, 2019 at 7:42 PM Biao Liu wrote:
> Hi Abdul, "--classpath " can be used for those are not included in
> user jar. If all your classes are included in your jar passed to Flink, you
> don't need this "--classpath".
>
> Abdul Qadee
Hi Abdul, "--classpath " can be used for those are not included in
user jar. If all your classes are included in your jar passed to Flink, you
don't need this "--classpath".
Abdul Qadeer 于2019年6月18日周二 上午3:08写道：
> Hi!
>
> I was going through submission of a Flink program through CLI. I see that
>
