Re: Getting around Serializability issues for types not in my control

2015-03-23 Thread Adelbert Chang
>>>> - field (class: >>>> dielectric.syntax.RDDOps$$anonfun$traverse$extension$1, >>>> name: apConcat$1, type: interface scala.Function2) >>>> - object (class >>>> dielectric.syntax.RDDOps$$anonfun$traverse$extension$1,

Re: Getting around Serializability issues for types not in my control

2015-03-23 Thread Cody Koeninger
things Serializable, what >>> can I >>> do to make things Serializable? I considered something like >>> >>> implicit def applicativeSerializable[F[_]](implicit F: Applicative[F]): >>> SomeSerializableType[F] = >>> new SomeSerializable

Re: Getting around Serializability issues for types not in my control

2015-03-23 Thread Adelbert Chang
de of submitting a PR to Scalaz to make things Serializable, what >> can I >> do to make things Serializable? I considered something like >> >> implicit def applicativeSerializable[F[_]](implicit F: Applicative[F]): >> SomeSerializableType[F] = >> new SomeSeria

Re: Getting around Serializability issues for types not in my control

2015-03-23 Thread Dean Wampler
mplicit def applicativeSerializable[F[_]](implicit F: Applicative[F]): > SomeSerializableType[F] = > new SomeSerializableType { ... } ?? > > Not sure how to go about doing it - I looked at java.io.Externalizable but > given `scalaz.Applicative` has no value members I'm not sure how to > imp

Getting around Serializability issues for types not in my control

2015-03-23 Thread adelbertc
ce would be much appreciated - thanks! -- View this message in context: http://apache-spark-user-list.1001560.n3.nabble.com/Getting-around-Serializability-issues-for-types-not-in-my-control-tp22193.html Sent from the Apache Spark User List mailing list archi