beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (BEAM-1623) Transform Reshuffle directly in Spark runner
Date Sun, 05 Mar 2017 05:16:32 GMT


ASF GitHub Bot commented on BEAM-1623:

GitHub user aviemzur opened a pull request:

    [BEAM-1623] Transform Reshuffle directly in Spark runner

    Be sure to do all of the following to help us incorporate your contribution
    quickly and easily:
     - [ ] 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).
     - [ ] 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](

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

    $ git pull translate-reshuffle

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

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

    This closes #2160
commit 6bc0241bb8d87f25f40ebef2682aab31b04a9fe9
Author: Aviem Zur <>
Date:   2017-03-05T05:15:32Z

    [BEAM-1623] Transform Reshuffle directly in Spark runner


> Transform Reshuffle directly in Spark runner
> --------------------------------------------
>                 Key: BEAM-1623
>                 URL:
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-spark
>            Reporter: Aviem Zur
>            Assignee: Aviem Zur
> Transform {{Reshuffle}} directly in Spark runner.
> Spark's {{repartition}} is logically equivalent to {{Reshuffle}} and will cause the required
fusion break without incurring the overhead of {{groupByKey}} (In streaming pipelines this
will use {{updateStateByKey}}) compared to a simple {{repartition}}.

This message was sent by Atlassian JIRA

View raw message