Github user tdas commented on the pull request:
https://github.com/apache/spark/pull/2624#issuecomment-57892709
@JoshRosen the simple fix is to delete the threadlocal variable completely.
Then any access to the threadlocal variable from any thread (even threadpool in
Py4J) is going to be reset.
---
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]
