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/09/26 13:04:20 UTC

[jira] [Commented] (FLINK-4677) Jars with no job executions produces NullPointerException in ClusterClient

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

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

GitHub user mxm opened a pull request:

    https://github.com/apache/flink/pull/2548

    [FLINK-4677] fail if user jar contains no executions

    If the user has an empty main method with no Flink executions, this will print a nicer error message.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/mxm/flink FLINK-4677

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/2548.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2548
    
----
commit 55f8ff766674b7c112a364de287b30a7afa4a1ee
Author: Maximilian Michels <mx...@apache.org>
Date:   2016-09-26T13:00:32Z

    [FLINK-4677] fail if user jar contains no executions

----


> Jars with no job executions produces NullPointerException in ClusterClient
> --------------------------------------------------------------------------
>
>                 Key: FLINK-4677
>                 URL: https://issues.apache.org/jira/browse/FLINK-4677
>             Project: Flink
>          Issue Type: Bug
>          Components: Client
>    Affects Versions: 1.2.0, 1.1.2
>            Reporter: Maximilian Michels
>            Assignee: Maximilian Michels
>            Priority: Minor
>             Fix For: 1.2.0, 1.1.3
>
>
> When the user jar contains no job executions, the command-line client displays a NullPointerException. This is not a big issue but should be changed to something more descriptive.



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