Markus,
On Tue, Nov 11, 2014 at 10:40 AM, M. Dale medal...@yahoo.com wrote:
I never tried to use this property. I was hoping someone else would jump
in. When I saw your original question I remembered that Hadoop has
something similar. So I searched and found the link below. A quick JIRA
Hi,
On Wed, Nov 5, 2014 at 10:23 AM, Tobias Pfeiffer wrote:
On Tue, Nov 4, 2014 at 8:33 PM, M. Dale wrote:
From http://spark.apache.org/docs/latest/configuration.html it seems
that there is an experimental property:
spark.files.userClassPathFirst
Thank you very much, I didn't know
Tobias,
From http://spark.apache.org/docs/latest/configuration.html it seems
that there is an experimental property:
spark.files.userClassPathFirst
Whether to give user-added jars precedence over Spark's own jars when
loading classes in Executors. This feature can be used to mitigate
Markus,
thanks for your help!
On Tue, Nov 4, 2014 at 8:33 PM, M. Dale medal...@yahoo.com.invalid wrote:
Tobias,
From http://spark.apache.org/docs/latest/configuration.html it seems
that there is an experimental property:
spark.files.userClassPathFirst
Thank you very much, I didn't
Hi,
I tried hard to get a version of netty into my jar file created with sbt
assembly that works with all my libraries. Now I managed that and was
really happy, but it seems like spark-submit puts an older version of netty
on the classpath when submitting to a cluster, such that my code ends up
