[
https://issues.apache.org/jira/browse/BEAM-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15899396#comment-15899396
]
ASF GitHub Bot commented on BEAM-1636:
--------------------------------------
GitHub user aviemzur opened a pull request:
https://github.com/apache/beam/pull/2180
[BEAM-1636] UnboundedDataset action() does not materialize RDD
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).
---
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/aviemzur/beam
unbounded-dataset-materialize-fix
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/beam/pull/2180.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 #2180
----
commit a889597e748eb752141af8dc568c56449c4eba5c
Author: Aviem Zur <[email protected]>
Date: 2017-03-07T13:07:03Z
[BEAM-1636] UnboundedDataset action() does not materialize RDD
----
> UnboundedDataset action() does not materialize RDD
> --------------------------------------------------
>
> Key: BEAM-1636
> URL: https://issues.apache.org/jira/browse/BEAM-1636
> Project: Beam
> Issue Type: Bug
> Components: runner-spark
> Reporter: Aviem Zur
> Assignee: Aviem Zur
>
> {{UnboundedDataset#action}} does not materialize DStream since it uses
> {{register}}. Instead use {{foreachRDD}}...{{foreach}} which is an action,
> which will materialize the RDDs of the DStream.
> The reason it worked until now was because there was also a call to
> {{cache()}} before it.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
