That is correct. You can provide it also as a property to the CLI:
-Denv.java.opts="-Dmy-prop=bla -Dmyprop2=bla2"
Cheers,
Till
On Sun, Apr 17, 2016 at 3:56 PM, Igor Berman wrote:
> for the sake of history(at task manager level):
> in conf/flink-conf.yaml
> env.java.opts: -Dmy-prop=bla -Dmy-prop
for the sake of history(at task manager level):
in conf/flink-conf.yaml
env.java.opts: -Dmy-prop=bla -Dmy-prop2=bla2
On 17 April 2016 at 16:25, Igor Berman wrote:
> How do I provide java arguments while submitting job? Suppose I have some
> legacy component that is dependent on java argument co
How do I provide java arguments while submitting job? Suppose I have some
legacy component that is dependent on java argument configuration.
I suppose Flink reuses same jvm for all jobs, so in general I can start
task manager with desired arguments, but then all my jobs can't have
different system
