flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maximilian Michels (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-2026) Error message in count() only jobs
Date Mon, 18 May 2015 10:30:00 GMT

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

Maximilian Michels commented on FLINK-2026:
-------------------------------------------

This is an issue many people run into, so let's see if we can do something about that. How
about a flag in the {{ExecutionEnvironment}} which indicates whether {{execute()}} has been
called before? This was also proposed in this discussion: https://www.mail-archive.com/dev@flink.apache.org/msg02145.html
alongside with a better error message in case of previous executions: 

{quote}
The Flink job didn't contain any sinks. This may be because the sinks were already executed.
If you executed the print() method on a DataSet before, the job would have already been executed.
In this case, remove the call of execute() until you have defined further sinks.
{quote}

> Error message in count() only jobs
> ----------------------------------
>
>                 Key: FLINK-2026
>                 URL: https://issues.apache.org/jira/browse/FLINK-2026
>             Project: Flink
>          Issue Type: Bug
>          Components: Core
>            Reporter: Sebastian Schelter
>            Priority: Minor
>
> If I run a job that only calls count() on a dataset (which is a valid data flow IMHO),
Flink executes the job but complains that no sinks are defined.



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

Mime
View raw message