Re: Propagation of exception message in GraphMapper

2012-03-29 Thread Dionysios Logothetis
Hi Avery, You are right. I just though it'd be better if this message appeared in the exception thrown by the GraphMapper, since this is the top one you see in the stack. This would make it easier to find out what's going on as opposed to have to search the stack trace. I think if you run a hadoop

Re: Propagation of exception message in GraphMapper

2012-03-28 Thread Avery Ching
Dionysis, I'm a little confused. The below message seems to explain the problem with Input path does not exist: hdfs://localhost:9000/x Am I missing something? Avery On 3/27/12 4:04 AM, Dionysis Logothetis wrote: Hi all, I was running one of the example apps and I accidentally entered

Propagation of exception message in GraphMapper

2012-03-27 Thread Dionysis Logothetis
Hi all, I was running one of the example apps and I accidentally entered the wrong input, so I ended up getting an exception from GraphMapper. But I think the actual cause of the exception (directory missing) is not propagated properly, which makes debugging a bit more difficult. Perhaps the gener