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-1815) Avoid shuffling twice in GABW
Date Mon, 27 Mar 2017 13:29:42 GMT


ASF GitHub Bot commented on BEAM-1815:

GitHub user amitsela opened a pull request:

    [BEAM-1815] Avoid shuffling twice in GABW.

    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 force-partitioner-gbk

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 #2334
commit 6221366bac567e5dccb01af0a1dc42bbaa499c8b
Author: Amit Sela <>
Date:   2017-03-27T12:30:03Z

    Force a "default" partitioner based on Spark default parallelism to avoid unnecessary
shuffles in
    the composite GBK implementation.


> Avoid shuffling twice in GABW
> -----------------------------
>                 Key: BEAM-1815
>                 URL:
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-spark
>            Reporter: Amit Sela
>            Assignee: Amit Sela
> Spark runner implementation of GABW includes a "built-in" groupByKey, but BOBK before
it already groups, so in order to avoid an unnecessary shuffle we need to force a {{Partitioner}}
on the RDDs involved. 

This message was sent by Atlassian JIRA

View raw message