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

ASF GitHub Bot commented on FLINK-2613:
---------------------------------------

Github user chiwanpark commented on a diff in the pull request:

    https://github.com/apache/flink/pull/1106#discussion_r41504243
  
    --- Diff: docs/apis/scala_shell.md ---
    @@ -30,15 +30,16 @@ Flink and setting up a cluster please refer to
     To use the shell with an integrated Flink cluster just execute:
     
     ~~~bash
    -bin/start-scala-shell.sh 
    +bin/start-scala-shell.sh local
     ~~~
     
     in the root directory of your binary Flink directory.
     
    -To use it with a running cluster you can supply the host and port of the 
JobManager with:
    +To use it with a running cluster start the scala shell with the keyword 
remote
    --- End diff --
    
    Ah I had a typo in line notes, grave accent(\`) would be better than 
quotation marks (").


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

Reply via email to