[
https://issues.apache.org/jira/browse/FLINK-5637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15837937#comment-15837937
]
ASF GitHub Bot commented on FLINK-5637:
---------------------------------------
Github user aljoscha commented on the issue:
https://github.com/apache/flink/pull/3216
Looks good, though we don't really test whether it silently ignores the
empty lines, do we?
> Default Flink configuration contains whitespace characters, causing parser
> WARNings
> -----------------------------------------------------------------------------------
>
> Key: FLINK-5637
> URL: https://issues.apache.org/jira/browse/FLINK-5637
> Project: Flink
> Issue Type: Bug
> Affects Versions: 1.2.0, 1.3.0
> Reporter: Robert Metzger
> Assignee: Robert Metzger
> Labels: starter
>
> {code}
> 2017-01-25 09:45:30,670 WARN
> org.apache.flink.configuration.GlobalConfiguration - Error while
> trying to split key and value in configuration file
> /yarn/nm/usercache/robert/appcache/application_1485249546281_0018/container_1485249546281_0018_01_000001/flink-conf.yaml:
>
> {code}
> The whitespace is currently in line 67:
> {code}
> #==============================================================================
>
> # The address under which the web-based runtime monitor listens.
> {code}
> I think we should add a test to the {{GlobalConfigurationTest}} that ensures
> the configuration file we are shipping doesn't produce any WARNings by
> default.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
