You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/04/01 20:42:25 UTC

[jira] [Commented] (FLINK-3560) Examples shouldn't always print usage statement

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

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

Github user StephanEwen commented on the pull request:

    https://github.com/apache/flink/pull/1752#issuecomment-204510235
  
    From my side, +1 for removing the `ProgramDescription` interface.
    
    I think it is a mismatch with the `main()` method based approach, because it needs to instantiate the class, while the general entry point is static. That does not go well together in my opinion. People will write programs with no default constructor. Previously, with the `Program` interface, such a constructor was also mandatory, it did fit better there.


> Examples shouldn't always print usage statement
> -----------------------------------------------
>
>                 Key: FLINK-3560
>                 URL: https://issues.apache.org/jira/browse/FLINK-3560
>             Project: Flink
>          Issue Type: Improvement
>          Components: Examples
>    Affects Versions: 1.0.0
>            Reporter: Till Rohrmann
>            Assignee: Till Rohrmann
>            Priority: Minor
>
> At the moment all our examples print a usage statement no matter whether the parameters have been provided or not. This can be confusing for people because an usage statement is usually only printed if one has specified a wrong parameter or if a parameter is missing.
> I propose to remove the unchecked printing of the usage statement.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)