Re: Spark log4j fully qualified class name

2016-02-29 Thread Steve Loughran
On 27 Feb 2016, at 20:40, Prabhu Joseph mailto:prabhujose.ga...@gmail.com>> wrote: Hi All, When i change the spark log4j.properties conversion pattern to know the fully qualified class name, all the logs has the FQCN as org.apache.spark.Logging. The actual fully qualified class name is ov

Re: Spark log4j fully qualified class name

2016-02-27 Thread Prabhu Joseph
Ted, That was a useful information. But i want it to use in development cluster to learn the internals through the logs. On Using %C, actual FQCN is not printed instead org.apache.spark.Logging overwrites. Is it a intended change in Spark. On Sun, Feb 28, 2016 at 3:46 AM, Ted Yu wrote: >

Re: Spark log4j fully qualified class name

2016-02-27 Thread Ted Yu
Looking at https://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/PatternLayout.html *WARNING* Generating the caller class information is slow. Thus, use should be avoided unless execution speed is not an issue. On Sat, Feb 27, 2016 at 12:40 PM, Prabhu Joseph wrote: > Hi All, > > Whe