Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/12598#discussion_r61048104
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/joins/HashedRelation.scala
---
@@ -324,7 +324,9 @@ private[joins] object UnsafeHashedRelation {
*
* see
http://java-performance.info/implementing-world-fastest-java-int-to-int-hash-map/
*/
-private[execution] final class LongToUnsafeRowMap(var mm:
TaskMemoryManager, capacity: Int)
+private[execution] final class LongToUnsafeRowMap(
+ @transient val mm: TaskMemoryManager,
--- End diff --
In generally, this type of 'fix' is actually wrong. If the object needs a
reference to this thing, then it won't work wherever it's deserialized. In some
cases, that happens to work out because the object is only accidentally
serialized and never used, or doesn't actually touch the transient field after
it's serialized. Is one of those the case here?
---
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]
