Skip to content
This repository has been archived by the owner on Jan 20, 2022. It is now read-only.

Use a FuturePool for blocking spark actions #511

Open
isnotinvain opened this issue May 21, 2014 · 0 comments
Open

Use a FuturePool for blocking spark actions #511

isnotinvain opened this issue May 21, 2014 · 0 comments
Labels

Comments

@isnotinvain
Copy link
Contributor

SparkPlatform submits blocking spark 'actions' in serial, but it should make (careful) use of a FuturePool instead, though we may run into spark thread-safety issues there. I actually had this implemented but didn't want to spend the time finding out whether spark is threadsafe in this way until I had something that worked in local mode first.

snoble pushed a commit to snoble/summingbird that referenced this issue Sep 8, 2017
Identity class and Monad instance
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant