Github user ericl commented on the issue:
https://github.com/apache/spark/pull/20927
Per @marmbrus 's suggestion also added a `SparkSession.active` call to
cover any edge case where the thread-local might not be set correctly. Spark
code should prefer to use this instead of getActive.get moving forward.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
