Github user jkbradley commented on the issue:
https://github.com/apache/spark/pull/18281
Catching up here, it sounds like the current recommendations (which I'm on
board with) are to:
* Switch to Futures, including using sameThreadExecutor for the case of
parallelism=1
* Try putting the use of Futures in a trait, unless it makes the code too
awkward. If @BryanCutler can reuse that in the other PR, that'd be great,
though it might require some generalization (if worthwhile).
* one or two smaller comments above
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
