You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Maximilian Michels (JIRA)" <ji...@apache.org> on 2015/09/04 09:40:45 UTC

[jira] [Comment Edited] (FLINK-2613) Print usage information for Scala Shell

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

Maximilian Michels edited comment on FLINK-2613 at 9/4/15 7:40 AM:
-------------------------------------------------------------------

OK, could we change this to 

{noformat}
Starting local Flink cluster (host: localhost, port 6123)
{noformat}

{noformat}
Connecting to Flink cluster (host: xyz, port 6123)
{noformat}

?


was (Author: mxm):
OK, could we change this to 

{noformat}
Starting local Flink cluster (host: localhost, port 6123)
{noformat}

{noformat}
Connecting to Flink cluster (host: xyz, port 6123)
{noformat}

> 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
>            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
(v6.3.4#6332)