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-22) DirectPipelineRunner: support for unbounded collections
Date Sat, 04 Jun 2016 00:59:59 GMT


ASF GitHub Bot commented on BEAM-22:

GitHub user tgroh opened a pull request:

    [BEAM-22] Remove improper Fn cloning

    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](
    The ParDoInProcessEvaluator is provided clones of a DoFn when
    appropriate, and should not serialize them.

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

    $ git pull remove_improper_cloning

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 #418
commit aa154e4ccf2e646069f80325ac8ec5f65a621382
Author: Thomas Groh <>
Date:   2016-06-04T00:57:24Z

    Remove improper Fn cloning
    The ParDoInProcessEvaluator is provided clones of a DoFn when
    appropriate, and should not serialize them.


> DirectPipelineRunner: support for unbounded collections
> -------------------------------------------------------
>                 Key: BEAM-22
>                 URL:
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-direct
>            Reporter: Davor Bonaci
>            Assignee: Thomas Groh
> DirectPipelineRunner currently runs over bounded PCollections only, and implements only
a portion of the Beam Model.
> We should improve it to faithfully implement the full Beam Model, such as add ability
to run over unbounded PCollections, and better resemble execution model in a distributed system.
> This further enables features such as a testing source which may simulate late data and
test triggers in the pipeline. Finally, we may want to expose an option to select between
"debug" (single threaded), "chaos monkey" (test as many model requirements as possible), and
"performance" (multi-threaded).
> more testing (chaos monkey) 
> Once this is done, we should update this StackOverflow question:

This message was sent by Atlassian JIRA

View raw message