the master itself.
> >
> >
> >
> > --
> > View this message in context:
> > http://apache-spark-user-list.1001560.n3.nabble.com/Classpath-errors-with-Breeze-tp7220p7225.html
> > Sent from the Apache Spark User List mailing list archive at Nabble.c
t;> --
>> View this message in context:
>> http://apache-spark-user-list.1001560.n3.nabble.com/Classpath-errors-with-Breeze-tp7220p7225.html
>> Sent from the Apache Spark User List mailing list archive at Nabble.com.
7;
> on EC2 on the master itself.
>
>
>
> --
> View this message in context:
> http://apache-spark-user-list.1001560.n3.nabble.com/Classpath-errors-with-Breeze-tp7220p7225.html
> Sent from the Apache Spark User List mailing list archive at Nabble.com.
Thanks for the quick response. No, I actually build my jar via 'sbt package'
on EC2 on the master itself.
--
View this message in context:
http://apache-spark-user-list.1001560.n3.nabble.com/Classpath-errors-with-Breeze-tp7220p7225.html
Sent from the Apache Spark User List mailing li
n't really
> know what's going on. Any thoughts?
>
>
>
>
>
>
> --
> View this message in context:
> http://apache-spark-user-list.1001560.n3.nabble.com/Classpath-errors-with-Breeze-tp7220.html
> Sent from the Apache Spark User List mailing list archive at Nabble.com.
s?
--
View this message in context:
http://apache-spark-user-list.1001560.n3.nabble.com/Classpath-errors-with-Breeze-tp7220.html
Sent from the Apache Spark User List mailing list archive at Nabble.com.