Thanks Sean.
On 19/01/16 13:36, Sean Owen wrote:
It's a good question. You can easily imagine an RDD of classes that
are mutable. Yes, if you modify these objects, the result is pretty
undefined, so don't do that.
On Tue, Jan 19, 2016 at 12:27 PM, Dave wrote:
Hi Marco,
Yes, that answers my q
It's a good question. You can easily imagine an RDD of classes that
are mutable. Yes, if you modify these objects, the result is pretty
undefined, so don't do that.
On Tue, Jan 19, 2016 at 12:27 PM, Dave wrote:
> Hi Marco,
>
> Yes, that answers my question. I just wanted to be sure as the API gav
; Am I correct in saying that these API's must never modify the data but
>> always return a new object with a copy of the data if the data needs to be
>> updated for the returned RDD.
>>
>> Thanks,
>> Dave.
>>
>>
>>
>> --
>> View this m
be
updated for the returned RDD.
Thanks,
Dave.
--
View this message in context:
http://apache-spark-user-list.1001560.n3.nabble.com/RDD-immutablility-tp26007.html
Sent from the Apache Spark User List mailing list archive at
Nabble.com.
-
API's (map, mapValues) give the developer access to the data stored
> in RDD's.
> Am I correct in saying that these API's must never modify the data but
> always return a new object with a copy of the data if the data needs to be
> updated for the returned RDD.
>
&
--
View this message in context:
http://apache-spark-user-list.1001560.n3.nabble.com/RDD-immutablility-tp26007.html
Sent from the Apache Spark User List mailing list archive at Nabble.com.
-
To unsubscribe, e-mail
