[
https://issues.apache.org/jira/browse/FLINK-943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephan Ewen resolved FLINK-943.
--------------------------------
Resolution: Fixed
Fix Version/s: 0.6-incubating
Fixed via b2bd4697af1984a00af3ded443b93528cf146769
> Configured values with double quotes are not parsed correctly in bash scripts
> -----------------------------------------------------------------------------
>
> Key: FLINK-943
> URL:
https://issues.apache.org/jira/browse/FLINK-943> Project: Flink
> Issue Type: Bug
> Reporter: Ufuk Celebi
> Fix For: 0.6-incubating
>
>
> In FLINK-942 I noticed that {{env.java.opts}} are not read by the startup scripts. While doing the fix I discovered a related problem:
> This works fine:
> {code}
> env.java.opts: -Dio.netty.leakDetectionLevel=paranoid
> {code}
> If you use it with double quotes, the startup scripts get messed up and don't even start up the JobManager/TaskManagers anymore:
> {code}
> env.java.opts: "-Dio.netty.leakDetectionLevel=paranoid"
> {code}
> This applies to all configuration values with double quotes and is there a seperate issue than FLINK-942. I just noticed it by chance for the JVM args.
--
This message was sent by Atlassian JIRA
(v6.2#6252)