Github user squito commented on the issue:
https://github.com/apache/spark/pull/19893
ok I just took a look at BroadcastExchangeExec, I see what you mean. It
isn't *that* bad, since spark isn't continually creating more instances of
those threads (you're not supposed to have more than one spark context in one
jvm anyway ...). But it also means a bad test could mess up that thread pool
(send it some task which never completes) and it would screw up all future
tests. I'd file a jira about it, but don't think you need to worry about it
for this change.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
