Re: spark.files.userClassPathFirst=true Not Working Correctly

2014-08-28 Thread DNoteboom
Sorry for the extremely late reply. It turns out that the same error occurred when running on yarn. However, I recently updated my project to depend on cdh5 and the issue I was having disappeared and I am no longer setting the userClassPathFirst to true. -- View this message in context: http:/

Re: spark.files.userClassPathFirst=true Not Working Correctly

2014-08-13 Thread DNoteboom
gt; > The option in Yarn is spark.yarn.user.classpath.first > > On Mon, Aug 11, 2014 at 1:33 PM, DNoteboom <[hidden email] > <http://user/SendEmail.jtp?type=node&node=12008&i=0>> wrote: > > > I'm currently running on my local machine on standalone.

Re: spark.files.userClassPathFirst=true Not Working Correctly

2014-08-11 Thread DNoteboom
I'm currently running on my local machine on standalone. The error shows up in my code when I am closing resources using the TaskContext.addOnCompleteCallBack. However, the cause of this error is because of a faulty classLoader which must occur in the Executor in the function createClassLoader.

spark.files.userClassPathFirst=true Not Working Correctly

2014-08-11 Thread DNoteboom
Currently my code uses commons-pool version 1.6 but Spark uses commons-pool version 1.54. This causes an error when I try to access a method that is visible in 1.6 but not in 1.54. I tried to fix this by setting the userClassPathFirst=true(and I verified that this was set correctly in http://:4040