You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/03/20 22:32:41 UTC
[jira] [Commented] (BEAM-1447) Autodetect streaming/not streaming
in DataflowRunner
[ https://issues.apache.org/jira/browse/BEAM-1447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15933731#comment-15933731 ]
ASF GitHub Bot commented on BEAM-1447:
--------------------------------------
GitHub user tgroh opened a pull request:
https://github.com/apache/beam/pull/2276
[BEAM-1447] Remove need for Streaming Flag in Dataflow
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](https://www.apache.org/licenses/icla.txt).
---
Autodetect if streaming is required, and if so run in Streaming.
I would love to have tests for this, but given the location it occurs,
I'm not sure how to do so effectively.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tgroh/beam automatic_streaming_dataflow
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/beam/pull/2276.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 #2276
----
commit 3ac32c7e0658089e6d28832ea7ade292d3a8d769
Author: Thomas Groh <tg...@google.com>
Date: 2017-03-20T21:40:05Z
Remove need for Streaming Flag in Dataflow
Autodetect if streaming is required, and if so run in Streaming.
----
> Autodetect streaming/not streaming in DataflowRunner
> ----------------------------------------------------
>
> Key: BEAM-1447
> URL: https://issues.apache.org/jira/browse/BEAM-1447
> Project: Beam
> Issue Type: Improvement
> Components: runner-dataflow
> Reporter: Kenneth Knowles
> Assignee: Thomas Groh
>
> Once pipeline surgery happens after construction, the Dataflow runner should be able to automatically decide how to execute a pipeline based on PCollection boundedness.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)