beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amit Sela (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (BEAM-649) Pipeline "actions" should use foreachRDD via ParDo.
Date Wed, 04 Jan 2017 17:55:58 GMT

    [ https://issues.apache.org/jira/browse/BEAM-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15798882#comment-15798882
] 

Amit Sela commented on BEAM-649:
--------------------------------

[~jbonofre] maybe we should rename this ticket to state what it actually will do - smarter
caching of RDDs.
We can add that it will solve BEAM-1206 (which is why it's closed on account of Duplicate).
As for Sink - we don't have an easy way to translate the Sink API specifically, but not sure
it would be necessary anymore.

> Pipeline "actions" should use foreachRDD via ParDo.
> ---------------------------------------------------
>
>                 Key: BEAM-649
>                 URL: https://issues.apache.org/jira/browse/BEAM-649
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-spark
>            Reporter: Amit Sela
>            Assignee: Jean-Baptiste Onofré
>
> Spark will execute a pipeline ONLY if it's triggered by an action (batch) / output operation
(streaming) - http://spark.apache.org/docs/1.6.2/streaming-programming-guide.html#output-operations-on-dstreams.
> Currently, such actions in Beam are mostly implemented via ParDo, and translated by the
runner as a Map transformation (via mapPartitions).
> The runner overcomes this by "forcing" actions on untranslated leaves.
> While this is OK, it would be better in some cases, e.g., Sinks, to apply the same ParDo
translation but with foreach/foreachRDD instead of foreachPartition/mapPartitions.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message