Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/12514#issuecomment-212572595
Yeah, as @rajeshbalamohan points out it looks like `KryoSerializer`'s
default is to enable reference tracking and that the SQL default here is
actually inconsistent with it:
https://github.com/apache/spark/blob/cb8ea9e1f34b9af287b3d10e47f24de4307c63ba/core/src/main/scala/org/apache/spark/serializer/KryoSerializer.scala#L71
Given this, the change here seems reasonable to me because it's actually
bringing the ThriftServer's behavior more in line with the defaults in Spark
Core. I wonder whether there's a cleaner way of doing this, though, perhaps by
setting `spark.kryo.referenceTracking` only if `maybeKryoReferenceTracking` is
defined.
---
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]
