[
https://issues.apache.org/jira/browse/FLINK-15053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16992467#comment-16992467
]
Yang Wang commented on FLINK-15053:
-----------------------------------
[~trohrmann], thanks for your comment. I will try to give a fix for this issue.
Could you assign this ticket to me?
This problem only comes up when the JM updated configuration contains space. If
the user puts config options in flink-conf.yaml or via `-yD`, it works fine.
Because we calculate the differences between client uploaded flink
configuration and JM updated configuration, then dynamic properties are used to
pass them to TaskManager.
Closing the quoting before escaping single quote should work. If the config
option value is my'value, the passing dynamic property will be
-Dkey1='my'\''value'.
> Configurations with values contains space may cause TM failures on Yarn
> -----------------------------------------------------------------------
>
> Key: FLINK-15053
> URL: https://issues.apache.org/jira/browse/FLINK-15053
> Project: Flink
> Issue Type: Bug
> Components: Deployment / YARN, Runtime / Coordination
> Affects Versions: 1.10.0
> Reporter: Xintong Song
> Priority: Blocker
> Fix For: 1.10.0
>
>
> Currently on Yarn setups, we are passing task executor specific
> configurations through dynamic properties in the starting command (see
> FLINK-13184).
> If the value of configuration contains space, the dynamic properties may not
> be correctly parsed, which could cause task executor failures. On occurrence
> can be found in FLINK-15047.
> It would be good to allow spaces when passing dynamic properties. E.g.,
> surrounding the values with double quotation marks, or escaping special
> characters.
> cc [~fly_in_gis]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
