flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-2613) Print usage information for Scala Shell
Date Tue, 15 Sep 2015 00:19:45 GMT

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

ASF GitHub Bot commented on FLINK-2613:

Github user fhueske commented on the pull request:

    The tests use the shell scripts (`.sh` or `.bat`) to start the Scala Shell and rely on
finding these scripts in the `flink-dist/target` folder. I think this is a bit fragile. Why
not directly using the `FlinkShell.scala` class?

> Print usage information for Scala Shell
> ---------------------------------------
>                 Key: FLINK-2613
>                 URL: https://issues.apache.org/jira/browse/FLINK-2613
>             Project: Flink
>          Issue Type: Improvement
>          Components: Scala Shell
>    Affects Versions: 0.10
>            Reporter: Maximilian Michels
>            Assignee: Nikolaas Steenbergen
>            Priority: Minor
>              Labels: starter
>             Fix For: 0.10
> The Scala Shell startup script starts a {{FlinkMiniCluster}} by default if invoked with
no arguments.
> We should add a {{--help}} or {{-h}} option to make it easier for people to find out
how to configure remote execution. Alternatively, we could print a notice on the local startup
explaining how to start the shell in remote mode.

This message was sent by Atlassian JIRA

View raw message