Re: class not found exception Logging while running JavaKMeansExample

2016-08-16 Thread Ted Yu
The class is: core/src/main/scala/org/apache/spark/internal/Logging.scala So it is in spark-core. On Tue, Aug 16, 2016 at 2:33 AM, subash basnet wrote: > Hello Yuzhihong, > > I didn't get how to implement what you said in the JavaKMeansExample.java. > As I get the logging

Re: class not found exception Logging while running JavaKMeansExample

2016-08-16 Thread subash basnet
Hello Yuzhihong, I didn't get how to implement what you said in the JavaKMeansExample.java. As I get the logging exception as while creating the spark session: Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/spark/internal/Logging at

Re: class not found exception Logging while running JavaKMeansExample

2016-08-15 Thread Ted Yu
Logging has become private in 2.0 release: private[spark] trait Logging { On Mon, Aug 15, 2016 at 9:48 AM, subash basnet wrote: > Hello all, > > I am trying to run JavaKMeansExample of the spark example project. I am > getting the classnotfound exception error: > *Exception

class not found exception Logging while running JavaKMeansExample

2016-08-15 Thread subash basnet
Hello all, I am trying to run JavaKMeansExample of the spark example project. I am getting the classnotfound exception error: *Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/spark/internal/Logging* at java.lang.ClassLoader.defineClass1(Native Method) at

Exception Logging

2014-10-16 Thread Ge, Yao (Y.)
I need help to better trap Exception in the map functions. What is the best way to catch the exception and provide some helpful diagnostic information such as source of the input such as file name (and ideally line number if I am processing a text file)? -Yao

Re: Exception Logging

2014-10-16 Thread Yana Kadiyska
you can out a try catch block in the map function and log the exception. The only tricky part is that the exception log will be located in the executor machine. Even if you don't do any trapping you should see the exception stacktrace in the executors' stderr log which is visible through the UI