Mailing-List: contact commits-help@beam.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@beam.apache.org
Date: Fri, 10 Mar 2017 07:06:04 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: commits@beam.incubator.apache.org
Message-ID: <JIRA.13015247.1477432161000.94.1489129564492@Atlassian.JIRA>
In-Reply-To: <JIRA.13015247.1477432161000@Atlassian.JIRA>
References: <JIRA.13015247.1477432161000@Atlassian.JIRA> <JIRA.13015247.1477432161817@jira-lw-us.apache.org>
Subject: [jira] [Commented] (BEAM-831) ParDo Chaining
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 10 Mar 2017 07:06:09 -0000


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

ASF GitHub Bot commented on BEAM-831:
-------------------------------------

GitHub user chinmaykolhatkar opened a pull request:

    https://github.com/apache/beam/pull/2216

    [BEAM-831] ParDo Chaining of Apex Runner

    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
    
     - [x] Make sure the PR title is formatted like:
       `[BEAM-<Jira issue #>] Description of pull request`
     - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable
           Travis-CI on your fork and ensure the whole test matrix passes).
     - [x] Replace `<Jira issue #>` in the title with the actual Jira issue
           number, if there is one.
     - [ ] If this contribution is large, please file an Apache
           [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.txt).
    
    R: @tweise, @kennknowles 
    ---
    
    This is currently Work in Progress PR. The tests are being developed. This PR was created to have a convenient environment for discussing this code. Here are the TODOS:
    1. Create the test cases for ParDo fusion for Apex runner


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/chinmaykolhatkar/beam BEAM-831_ParDoChaining

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/beam/pull/2216.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2216
    
----
commit d33532e607a5853f664602b3aae49c41a30bf046
Author: chinmaykolhatkar <chinmay@apache.org>
Date:   2017-03-01T11:29:46Z

    [BEAM-831] ParDo Fusion of Apex Runner

----


> ParDo Chaining
> --------------
>
>                 Key: BEAM-831
>                 URL: https://issues.apache.org/jira/browse/BEAM-831
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-apex
>            Reporter: Thomas Weise
>
> Current state of Apex runner creates a plan that will place each operator in a separate container (which would be processes when running on a YARN cluster). Often the ParDo operators can be collocated in same thread or container. Use Apex affinity/stream locality attributes for more efficient execution plan.  


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)