Re: Customizing the classpath for TM and JM

Posted by Alexander Alexandrov on
URL: http://deprecated-apache-flink-user-mailing-list-archive.369.s1.nabble.com/Customizing-the-classpath-for-TM-and-JM-tp624p627.html

Sorry, I meant between the three. In particular, where will env.java.classpath propagate?

2015-01-15 14:24 GMT+01:00 Alexander Alexandrov <[hidden email]>:

No worries, this is the first reply that I get in this thread.

What would be the difference between the two? I can make a PR if we agree on that.

2015-01-15 11:28 GMT+01:00 Ufuk Celebi <[hidden email]>:

Hey Alexander,

there is only the option "env.java.opts", which can be set in the config. I think you cannot use this to have multiple "-classpath" options when starting Java?

It makes sense to have the option to add something to the classpath. I will check this and fix it. :-) What about "taskmanager.env.java.classpath" and "jobmanager.env.java.classpath" as a configuration key? And maybe an additional "env.java.classpath"?

PS: sorry for the incomplete mail before :D

On 15 Jan 2015, at 01:00, Alexander Alexandrov <[hidden email]> wrote:

> Hi there,
>
> is there a canonical / suggested way to customize the classpath of the Flink JM and TM processes?
>
> At the moment I hardcoded my way around this by manually changing the following lines like that:
>
> # in taskmanager.sh
> $JAVA_RUN [...] -classpath "/tmp/classes:$FLINK_TM_CLASSPATH"
>
> # in jobmanagre.sh
> $JAVA_RUN [...] -classpath "/tmp/classes:$FLINK_JM_CLASSPATH"
>
> Perhaps there is a variable that I can set in conf/flink.yaml that will do the same trick.