flink-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephan Ewen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-943) Configured values with double quotes are not parsed correctly in bash scripts
Date Tue, 17 Jun 2014 11:53:02 GMT

    [ https://issues.apache.org/jira/browse/FLINK-943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14033701#comment-14033701
] 

Stephan Ewen commented on FLINK-943:
------------------------------------

Is the issue in the bash-based yaml parser, or in the way that the variables are concatenated
to build the java arguments?

> 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)

Mime
View raw message