[jira] [Created] (FLINK-943) Configured values with double quotes are not parsed correctly in bash scripts

Posted by Shang Yuanchun (Jira) on Jun 16, 2014; 11:05pm
URL: http://deprecated-apache-flink-mailing-list-archive.368.s1.nabble.com/jira-Created-FLINK-943-Configured-values-with-double-quotes-are-not-parsed-correctly-in-bash-scripts-tp304.html

Ufuk Celebi created FLINK-943:
---------------------------------

             Summary: 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


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)