And if the content is not immutable, we can change its content, but
>> cannot
>> > add / remove data?
>> >
>> >
>> >
>> >
>> > --
>> > View this message
> I see, so in order the RDD to be completely immutable, its content
> should be
> > immutable as well.
> >
> > And if the content is not immutable, we can change its content, but
> cannot
> > add / remove data?
> >
> >
> >
> >
> > --
> >
ely immutable, its content should be
> immutable as well.
>
> And if the content is not immutable, we can change its content, but cannot
> add / remove data?
>
>
>
>
> --
> View this message in context:
> http://apache-spark-developers-list.1001551.n3.nabble.com/RDD-Vec
I see, so in order the RDD to be completely immutable, its content should be
immutable as well.
And if the content is not immutable, we can change its content, but cannot
add / remove data?
--
View this message in context:
http://apache-spark-developers-list.1001551.n3.nabble.com/RDD-Vector
14814814814814817,0.09876543209876545]
> [0.0,0.49119985188436205]
>
>
>
> But how can this be that my method changes the Immutable RDD?
>
> BTW, the signature of the train method, is the following:
>
> train( data: RDD[Vector],
.n3.nabble.com/RDD-Vector-Immutability-issue-tp15827p15829.html
Sent from the Apache Spark Developers List mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org
For additional commands, e
ext:
http://apache-spark-developers-list.1001551.n3.nabble.com/RDD-Vector-Immutability-issue-tp15827p15828.html
Sent from the Apache Spark Developers List mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: de
http://apache-spark-developers-list.1001551.n3.nabble.com/RDD-Vector-Immutability-issue-tp15827.html
Sent from the Apache Spark Developers List mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: dev-unsubscr...@spark.apa
