[
https://issues.apache.org/jira/browse/FLINK-2613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14734731#comment-14734731
]
Nikolaas Steenbergen commented on FLINK-2613:
---------------------------------------------
I've added some additional new-lines for the starting-connecting messages to
make them more visible.
I think [~mxm] is right, the user cant be unaware of the startup mode now that
he has to explicitly type it.
The other thing is that the FlinkILoop handles the startup message (squirrel),
but is agnostic to the startup mode (it always connects through host and port),
we would need to explicitly tell it the startup mode, just to print it below
the squirrel, i think its nicer (codewise) the way it is now..
> 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)
