Spark isolates each task, so I would use the MLlib vector. I didn't mention this, but it also integrates with Breeze, a Scala mathematics library that you might find useful.
dean Dean Wampler, Ph.D. Author: Programming Scala, 2nd Edition <http://shop.oreilly.com/product/0636920033073.do> (O'Reilly) Typesafe <http://typesafe.com> @deanwampler <http://twitter.com/deanwampler> http://polyglotprogramming.com On Sat, Oct 4, 2014 at 8:52 AM, ll <[email protected]> wrote: > thanks dean. thanks for the answer with great clarity! > > i'm working on an algorithm that has a weight vector W(w0, w1, .., wN). > the > elements of this weight vector are adjusted/updated frequently - every > iteration of the algorithm. how would you recommend to implement this > vector? what is the best practice to implement this in Scala & Spark? > > > > -- > View this message in context: > http://apache-spark-user-list.1001560.n3.nabble.com/scala-Vector-vs-mllib-Vector-tp15736p15741.html > Sent from the Apache Spark User List mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
