[
https://issues.apache.org/jira/browse/BEAM-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15214814#comment-15214814
]
ASF GitHub Bot commented on BEAM-22:
------------------------------------
GitHub user tgroh opened a pull request:
https://github.com/apache/incubator-beam/pull/82
[BEAM-22] Execute ModelEnforcements in TransformExecutor
This allows a configurable application of Model Enforcement based on the
class of transform being executed, both before and after an element is
processed and after the transform completes.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tgroh/incubator-beam
ippr_model_enforcing_transform_executor
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-beam/pull/82.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 #82
----
commit b76b9d62f2a21e534238437f0e6aa34321146007
Author: Thomas Groh <tg...@google.com>
Date: 2016-03-28T16:35:33Z
Execute ModelEnforcements in TransformExecutor
This allows a configurable application of Model Enforcement based on the
class of transform being executed, both before and after an element is
processed and after the transform completes.
----
> 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)
