Uma, Harsh, and Steve, Thank you all for the explanation. I really appreciate it.
I guess it is just ignorant of me of not knowing this as a mere debug printing technique. In my little world, every exception is a cause of alarm ... and I can't tell the difference in this case when I try to use the configuration and customize. I thought my core-site.xml was not found or read properly. If I had dump'ed the whole thing - it should be behaving properly despite the *printed* exception. Best Regard, Ruby On Thu, Sep 29, 2011 at 6:33 AM, Steve Loughran <ste...@apache.org> wrote: > On 29/09/11 02:40, Ruby Stevenson wrote: >> >> hmm ... I tried a small test program, if I put log4j configuration in the >> classpath and turn on debug level, I am actually seeing the exception >> thrown. The seemingly silly issue I had have been bugging me for a while. >> >> >> DEBUG hadoop.conf.Configuration - java.io.IOException: config() >> at org.apache.hadoop.conf.Configuration.<init>(Configuration.java:226) >> at org.apache.hadoop.conf.Configuration.<init>(Configuration.java:213) >> > > It's to help track down where things get configured >
