Github user sryza commented on a diff in the pull request:
https://github.com/apache/spark/pull/789#discussion_r18053706
--- Diff: core/src/main/scala/org/apache/spark/SparkConf.scala ---
@@ -140,6 +142,20 @@ class SparkConf(loadDefaults: Boolean) extends
Cloneable with Logging {
this
}
+ /**
+ * Use Kryo serialization and register the given set of classes with
Kryo.
+ * If called multiple times, this will append the classes from all calls
together.
+ */
+ def registerKryoClasses(classes: Seq[Class[_ <: Any]]): SparkConf = {
+ val allClassNames = new LinkedHashSet[String]()
--- End diff --
Here's a thread that indicates order is important, at least in the sense
that the kryo instance serializing should have the same order as the instance
deserializer:
https://groups.google.com/forum/#!topic/kryo-users/E-0_EVi-O1Q
String's hash code is deterministic, so it shouldn't really matter, but I
think it doesn't hurt to be conservative.
The LinkedHashSet should preserve order, unless I'm missing something?
---
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]
