Github user reggert commented on the pull request:
https://github.com/apache/spark/pull/9264#issuecomment-158783297
SparkQA seems to be happy now.
@JoshRosen What else needs to be done to move forward on this? The current
implementation on master requires a dedicated thread pool for all callbacks on
FutureActions to avoid depleting the global ExecutionContext (and this fact is
entirely undocumented), so it would be good to have these changes in 1.6.
---
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]
