On Wed, 21 Nov 2018 at 05:26, clay wrote:
> hi
>
> I have checked all the dependences, and don't find the jar with different
> version, so ,I double the way to submit jar has some issue? my commend is
> like this:
>
Did you also check the runtime dependencies where the code is run? Because
t
hi yinhua,
I consirdered about that way,but I don't think that way is suitable ,
because I want each flink job has its own business logic and dependence jar
,separate from other job, that's what I want to do,
--
Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/
As far as I know, -yt works for both job manager and task manager, -C works
for flink cli.
Did you consider putting all your jars in /flink/lib?
--
Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/
hi
I have checked all the dependences, and don't find the jar with different
version, so ,I double the way to submit jar has some issue? my commend is
like this:
/data/flink1.6/bin/flink run -m yarn-cluster -ytm 8032 -yn 1 -ys 1 -yqu
-yt /data/flink1.6//lib -c com.xxx.xxx.xxx.Launch -C
My only guess would be that you have two versions of the Apache Commons jar on
your class path, or the version you compiled against doesn’t match what you’re
running against, and that’s why you get:
Caused by: java.lang.ClassCastException: cannot assign instance of
org.apache.commons.collection
hi all:
I know that when submitting flink jobs, flink's official recommendation is
to put all the dependencies and business logic into a fat jar, but now our
requirement is to separate the business logic and rely on dynamic commits,
so I found one. One way, use the -yt and -C parameters to submit
