plab/shark/blob/master/src/main/scala/shark/execution/serialization/KryoSerializationWrapper.scala>
Don't you think it's a good idea to have something like this inside the
framework itself? :)
--
View this message in context:
http://apache-spark-developers-list.1001551.n3.nabbl
Thanks for sending this in.
The ASF list doesn't support html so the formatting of the code is a little
messed up. For those who want to see the code in clearly formatted text, go
to
http://apache-spark-developers-list.1001551.n3.nabble.com/Kryo-serialization-for-closures-a-workaround-tp6787
day, May 24, 2014 10:32:57 AM
> Subject: Kryo serialization for closures: a workaround
>
> Suppose my mappers can be functions (def) that internally call other classes
> and create objects and do different things inside. (Or they can even be
> classes that extend (Foo) => Bar and
