[
https://issues.apache.org/jira/browse/FLINK-17827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated FLINK-17827:
-----------------------------------
Labels: pull-request-available starter (was: starter)
> 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
>
> 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)
