You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Stephan Ewen (JIRA)" <ji...@apache.org> on 2014/11/20 20:55:34 UTC
[jira] [Resolved] (FLINK-820) Support for unconnected data flows
[ https://issues.apache.org/jira/browse/FLINK-820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephan Ewen resolved FLINK-820.
--------------------------------
Resolution: Fixed
Fix Version/s: (was: pre-apache)
0.8-incubating
Assignee: Stephan Ewen
Fixed via 98ff76b0ea61a342250e15411edd9f7974cbe96d
> Support for unconnected data flows
> ----------------------------------
>
> Key: FLINK-820
> URL: https://issues.apache.org/jira/browse/FLINK-820
> Project: Flink
> Issue Type: Improvement
> Reporter: GitHub Import
> Assignee: Stephan Ewen
> Labels: github-import
> Fix For: 0.8-incubating
>
>
> Currently the compiler fails when given a plan with separate data flows.
> ```java
> throw new CompilerException("The given Pact program contains multiple disconnected data flows.");
> ```
> However, I do not see a good conceptual reason to not support such data flows. Are there any technical issues?
> To elaborate a bit on the issue: I have a higher level operator that may or may not produce separated data flows. In a current workaround I have to pipe the union of all data flows to a dummy sink to avoid such an exception.
> ---------------- Imported from GitHub ----------------
> Url: https://github.com/stratosphere/stratosphere/issues/820
> Created by: [AHeise|https://github.com/AHeise]
> Labels:
> Created at: Thu May 15 16:51:46 CEST 2014
> State: open
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)