hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan A. Pendleton" ...@geekdom.net>
Subject Re: svn commit: r376492 - /lucene/hadoop/trunk/src/java/org/apache/hadoop/mapred/JobConf.java
Date Fri, 10 Feb 2006 00:21:36 GMT
I agree that the first fix is better (handling the file: part of the URL).

I don't quite agree about not setting a Jar file masking the problem -
certainly, testing things out in debugging environments makes it not
guaranteed that there's a Jar there. In any case, it would certainly be
better to fail-fast there, but, at this point, fail-fast by obscure NPE
isn't necessarily better. Is there something better?

On 2/9/06, Owen O'Malley <owen@yahoo-inc.com> wrote:
> Actually, I liked the first fix for the java 1.4 problem better (489
> rather than 492), since it was shorter and more concise.
> Furthermore, I think that it is a serious mistake to mask the problem
> of not finding the jar file. For map/reduce, the application will fail
> without the jar set. Having it fail at the right spot in the driver is
> much better than having it fail in the task tracker with Class Not
> Found.
> -- Owen

Bryan A. Pendleton
Ph: (877) geek-1-bp
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message