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 Thu, 07 Apr 2016 18:50:25 GMT


ASF GitHub Bot commented on BEAM-22:

GitHub user tgroh opened a pull request:

    [BEAM-22] Clear Empty TransformExecutorServices

    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`
     - [x] 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.
     - [x] If this contribution is large, please file an Apache
           [Individual Contributor License Agreement](
    This reduces the amount of objects tracked by the ExecutorServiceParallelExecutor
    when keys stop appearing. If this is not done, as new keys show up and no more
    work appears for old keys, the number of TransformExecutorServices grows, and
    we maintain a reference for all of them.

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

    $ git pull ippr_empty_evaluation_state

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 #143
commit 066ae4526c229f1e9c11172aae82aaccbde09c42
Author: Thomas Groh <>
Date:   2016-03-29T17:27:37Z

    Schedule all pending work before firing timers
    Pull all available work off of the ExecutorUpdate queue during each
    execution of the MonitorRunnable.

commit c3ae8460b0f49bcb5d6d5e47d29152ccc411bf99
Author: Thomas Groh <>
Date:   2016-03-29T17:56:10Z

    Clean up empty TransformExecutorServices
    This allows the size of the currentEvaluations map in
    ExecutorServiceParallelExecutor to be based on the number of keys for
    serial computations that are currently in-progress, rather than
    the number of keys for serializable computations for the entire life of
    the pipeline.


> 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