This is worth a look: https://github.com/apache/spark/pull/24085
Scala has a surprising thread-safety bug in the "<:<" operator that's used to check subtypes, which can lead to incorrect results in non-trivial situations. The fix on the table is to introduce a global lock to protect a lot of the Scala-related reflection code to resolve it. This may be the best we can do, but 'global lock' sounds ominous. Any thoughts on other ways to resolve it? I'm not sure there are. --------------------------------------------------------------------- To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
