[
https://issues.apache.org/jira/browse/BEAM-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15172410#comment-15172410
]
ASF GitHub Bot commented on BEAM-22:
------------------------------------
GitHub user tgroh opened a pull request:
https://github.com/apache/incubator-beam/pull/3
[BEAM-22] Support Unbounded PCollections in same-process execution
This completes the implementation of the InProcessPipelineRunner, which is
capable of running over unbounded inputs.
Existing Unit Tests built on the DirectPipelineRunner all pass, with the
exception of ParDoTest, which has a gap in immutability and encodability
testing. This change does not migrate existing unit tests to run on the
InProcessPipelineRunner.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tgroh/incubator-beam
in_process_pipeline_runner
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-beam/pull/3.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 #3
----
commit aa49f92aec9fe89e9c6ffd0c972219e283685387
Author: Thomas Groh <[email protected]>
Date: 2016-02-27T01:28:37Z
Implement InProcessEvaluationContext
This is the primary "global state" object for the evaluation of a
Pipeline using the InProcessPipelineRunner, and is responsible for
properly routing information about the state of the pipeline to
transform evaluators.
Remove the InProcessEvaluationContext from the InProcessPipelineRunner
class, and implement as a class directly. Fix associated imports.
commit 54fe0ff31c1f94248b9a59612482f83529edf81f
Author: Thomas Groh <[email protected]>
Date: 2016-02-27T01:29:43Z
Add ExecutorServiceParallelExecutor as an InProcessExecutor
This is responsible for scheduling transform evaluations and
communicating results back to the evaluation context. The executor
handle PTransforms that block arbitarily waiting for additional input.
commit 5feea5b79903c85baf8677351ad65557efb523f3
Author: Thomas Groh <[email protected]>
Date: 2016-02-27T01:30:13Z
Implement InProcessPipelineRunner#run
Appropriately construct an evaluation context and executor, and start
the pipeline when run is called.
Implement runner-provided ExecutionContext and StepContext abstractions.
----
> DirectPipelineRunner: support for unbounded collections
> -------------------------------------------------------
>
> Key: BEAM-22
> URL: https://issues.apache.org/jira/browse/BEAM-22
> 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:
> http://stackoverflow.com/questions/35350113/testing-triggers-with-processing-time/35401426#35401426
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
