Return-Path: X-Original-To: apmail-flink-issues-archive@minotaur.apache.org Delivered-To: apmail-flink-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CD46918001 for ; Thu, 9 Jul 2015 08:49:04 +0000 (UTC) Received: (qmail 63926 invoked by uid 500); 9 Jul 2015 08:49:04 -0000 Delivered-To: apmail-flink-issues-archive@flink.apache.org Received: (qmail 63882 invoked by uid 500); 9 Jul 2015 08:49:04 -0000 Mailing-List: contact issues-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flink.apache.org Delivered-To: mailing list issues@flink.apache.org Received: (qmail 63787 invoked by uid 99); 9 Jul 2015 08:49:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Jul 2015 08:49:04 +0000 Date: Thu, 9 Jul 2015 08:49:04 +0000 (UTC) From: "Gyula Fora (JIRA)" To: issues@flink.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (FLINK-2328) Applying more than one transformation on an IterativeDataStream fails MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/FLINK-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gyula Fora updated FLINK-2328: ------------------------------ Component/s: Streaming > Applying more than one transformation on an IterativeDataStream fails > --------------------------------------------------------------------- > > Key: FLINK-2328 > URL: https://issues.apache.org/jira/browse/FLINK-2328 > Project: Flink > Issue Type: Bug > Components: Streaming > Reporter: Gyula Fora > Assignee: Gyula Fora > > Currently the user cannot apply more than one transformation on the IterativeDataStream directly. > It fails because instead of creating one iteration source and connecting it to the operators it will try to create two iteration sources which fails on the shared broker slot. > A workaround is to use a no-op mapper on the iterative stream and applying the two transformations on that. -- This message was sent by Atlassian JIRA (v6.3.4#6332)