[
https://issues.apache.org/jira/browse/FLINK-17827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chesnay Schepler closed FLINK-17827.
------------------------------------
Fix Version/s: 1.13.0
Resolution: Fixed
master: 507e7c57af0d2c5ca5f6ff7e918355a6399bcc7e
> scala-shell.sh should fail early if no mode is specified, or have default
> logging settings
> ------------------------------------------------------------------------------------------
>
> Key: FLINK-17827
> URL: https://issues.apache.org/jira/browse/FLINK-17827
> Project: Flink
> Issue Type: Improvement
> Components: Scala Shell
> Affects Versions: 1.11.0
> Reporter: Chesnay Schepler
> Priority: Critical
> Labels: pull-request-available, starter
> Fix For: 1.13.0
>
>
> The scala-shell has multiple modes it can run in: local, remote and yarn.
> It is mandatory to specify such a mode, but this is only enforced on the
> scala side, not in the bash script.
> The problem is that the scala-shell script derives the log4j properties from
> the mode, and if no mode is set, then the log4j properties are empty.
> This leads to a warning from slf4j that no logger was defined and all that.
> Either scala-shell.sh should fail early if no mode is specified, or it should
> have some default logging settings (e.g., the ones for local/remote).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
