[ 
https://issues.apache.org/jira/browse/SPARK-13700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Paulo Costa updated SPARK-13700:
--------------------------------
    Description: 
Spark is great for synchronous operations.

But sometimes I need to call a database/web server/etc from my transform, and 
the Spark pipeline stalls waiting for it.

Avoiding that would be great!

I suggest we add a new method RDD.mapAsync(), which can execute these 
operations concurrently, avoiding the bottleneck.

I've written a quick'n'dirty implementation of what I have in mind: 
https://gist.github.com/paulo-raca/d121cf27905cfb1fafc3

What do you think?

If you agree with this feature, I can work on a pull request.

  was:
Spark is great for synchronous operations.

But sometimes I need to call a web database/web server/etc from my transform, 
and the Spark pipeline stalls waiting for it.

Avoiding that would be great!

I suggest we add a new method RDD.mapAsync(), which can execute these 
operations concurrently, avoiding the bottleneck.

I've written a quick'n'dirty implementation of what I have in mind: 
https://gist.github.com/paulo-raca/d121cf27905cfb1fafc3

What do you think?

If you agree with this feature, I can work on a pull request.


> Rdd.mapAsync(): Easily mix Spark and asynchroneous transformation
> -----------------------------------------------------------------
>
>                 Key: SPARK-13700
>                 URL: https://issues.apache.org/jira/browse/SPARK-13700
>             Project: Spark
>          Issue Type: Improvement
>          Components: Spark Core
>    Affects Versions: 1.6.0
>            Reporter: Paulo Costa
>            Priority: Minor
>              Labels: async, features, rdd, transform
>
> Spark is great for synchronous operations.
> But sometimes I need to call a database/web server/etc from my transform, and 
> the Spark pipeline stalls waiting for it.
> Avoiding that would be great!
> I suggest we add a new method RDD.mapAsync(), which can execute these 
> operations concurrently, avoiding the bottleneck.
> I've written a quick'n'dirty implementation of what I have in mind: 
> https://gist.github.com/paulo-raca/d121cf27905cfb1fafc3
> What do you think?
> If you agree with this feature, I can work on a pull request.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org

Reply via email to