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 2D4C1200D2E for ; Tue, 31 Oct 2017 20:00:08 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 2BE431609E6; Tue, 31 Oct 2017 19:00:08 +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 70E6E1609EF for ; Tue, 31 Oct 2017 20:00:07 +0100 (CET) Received: (qmail 84737 invoked by uid 500); 31 Oct 2017 19:00:06 -0000 Mailing-List: contact commits-help@beam.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@beam.apache.org Delivered-To: mailing list commits@beam.apache.org Received: (qmail 84726 invoked by uid 99); 31 Oct 2017 19:00:06 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 31 Oct 2017 19:00:06 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id D41B3180784 for ; Tue, 31 Oct 2017 19:00:05 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 8EHzf-a7biJV for ; Tue, 31 Oct 2017 19:00:05 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id B496660F56 for ; Tue, 31 Oct 2017 19:00:04 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id F36BAE041C for ; Tue, 31 Oct 2017 19:00:03 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id B365A212F8 for ; Tue, 31 Oct 2017 19:00:02 +0000 (UTC) Date: Tue, 31 Oct 2017 19:00:02 +0000 (UTC) From: "Daniel Oliveira (JIRA)" To: commits@beam.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (BEAM-3124) Get flattens working with portability. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 31 Oct 2017 19:00:08 -0000 [ https://issues.apache.org/jira/browse/BEAM-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Daniel Oliveira updated BEAM-3124: ---------------------------------- Description: Some adjustments need to be made to the way flattens are handled to the get them working for portability. Ideally flattens should be present in the execution graphs, there should be no DoFns with multiple inputs, and flattens should execute on either the system runners or SDK runners when appropriate. (was: Some adjustments need to be made to the way flattens are handled to the get them working for portability. Currently flattens are removed from execution and the PCollections received by the flatten are instead sent to the DoFns that consume the flatten. Ideally flattens should actually present in the execution graphs to avoid having DoFns with multiple inputs, and they should be able to execute on either the system runners or SDK runners when appropriate.) > Get flattens working with portability. > -------------------------------------- > > Key: BEAM-3124 > URL: https://issues.apache.org/jira/browse/BEAM-3124 > Project: Beam > Issue Type: Improvement > Components: beam-model > Reporter: Daniel Oliveira > Assignee: Daniel Oliveira > Labels: portability > > Some adjustments need to be made to the way flattens are handled to the get them working for portability. Ideally flattens should be present in the execution graphs, there should be no DoFns with multiple inputs, and flattens should execute on either the system runners or SDK runners when appropriate. -- This message was sent by Atlassian JIRA (v6.4.14#64029)