[
https://issues.apache.org/jira/browse/BEAM-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davor Bonaci updated BEAM-22:
-----------------------------
Description:
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
was:
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.
Once this is done, we should update this StackOverflow question:
http://stackoverflow.com/questions/35350113/testing-triggers-with-processing-time/35401426#35401426
> 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)
