Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id A25EA200C4C for ; Tue, 4 Apr 2017 10:59:35 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id A0F47160B90; Tue, 4 Apr 2017 08:59:35 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id DEC56160B81 for ; Tue, 4 Apr 2017 10:59:34 +0200 (CEST) Received: (qmail 61186 invoked by uid 500); 4 Apr 2017 08:59:34 -0000 Mailing-List: contact dev-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 dev@flink.apache.org Received: (qmail 61174 invoked by uid 99); 4 Apr 2017 08:59:33 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Apr 2017 08:59:33 +0000 Received: from [192.168.178.115] (ipservice-092-219-046-010.092.219.pools.vodafone-ip.de [92.219.46.10]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 3AF771A00E8; Tue, 4 Apr 2017 08:59:32 +0000 (UTC) From: Aljoscha Krettek Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: Flink limitations under Beam Date: Tue, 4 Apr 2017 10:59:29 +0200 References: <1082216090.9473606.1491264704712.ref@mail.yahoo.com> <1082216090.9473606.1491264704712@mail.yahoo.com> To: dev@flink.apache.org, amir bahmanyari In-Reply-To: <1082216090.9473606.1491264704712@mail.yahoo.com> Message-Id: <42087757-9D91-4D95-AD96-27449B358E15@apache.org> X-Mailer: Apple Mail (2.3273) archived-at: Tue, 04 Apr 2017 08:59:35 -0000 Hi, I think you would mainly lose on performance, since Beam adds an = additional layer of abstraction and has some requirements from Runners = that slow things down compared to running natively on Flink. I think feature wise, the only thing that you will lose is support for = Iterations/feedback edges. Flink has this while Beam does not (yet) have = an API for that. Best, Aljoscha=20 > On 4. Apr 2017, at 02:11, amir bahmanyari = wrote: >=20 > Hi colleagues, been a long time. New project.What = feature(s)/capabilities of Flink would become unavailable/limited if the = pipeline app is written in Beam sdk using FlinkRunner? > Thanks+regards