Return-Path: Delivered-To: apmail-lucene-hadoop-dev-archive@locus.apache.org Received: (qmail 89633 invoked from network); 14 Jun 2006 19:31:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 14 Jun 2006 19:31:37 -0000 Received: (qmail 28168 invoked by uid 500); 14 Jun 2006 19:28:32 -0000 Delivered-To: apmail-lucene-hadoop-dev-archive@lucene.apache.org Received: (qmail 25855 invoked by uid 500); 14 Jun 2006 19:28:19 -0000 Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hadoop-dev@lucene.apache.org Delivered-To: mailing list hadoop-dev@lucene.apache.org Received: (qmail 25213 invoked by uid 99); 14 Jun 2006 19:28:12 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Jun 2006 12:28:12 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Jun 2006 12:08:43 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id D2CD371428D for ; Wed, 14 Jun 2006 19:07:29 +0000 (GMT) Message-ID: <205898.1150312049860.JavaMail.jira@brutus> Date: Wed, 14 Jun 2006 19:07:29 +0000 (GMT+00:00) From: "Benjamin Reed (JIRA)" To: hadoop-dev@lucene.apache.org Subject: [jira] Created: (HADOOP-303) JobClient looking for classes for submitted job in the wrong place MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N JobClient looking for classes for submitted job in the wrong place ------------------------------------------------------------------ Key: HADOOP-303 URL: http://issues.apache.org/jira/browse/HADOOP-303 Project: Hadoop Type: Bug Components: mapred Versions: 0.3.2 Reporter: Benjamin Reed Priority: Minor JobClient does some checking of the job being submitted when it submits a jar file along with the job. The problem is that the JobClient pulls classes from the classpath rather than the submitted jar file. Because the jar file may contain newer (or older) versions of classes on the classpath this behavior leads to confusing errors when the job is run. It is also a pain to ensure that the jar file being submitted is on the classpath. Further, if the JobClient uses the submitted jar file rather than the classpath, missing classes from the jar file can be detected earlier. This patch will cause the JobClient to load the classes for a job from the jar file rather than the classpath. Because of the class loading precedence rules in Java, if the class is on the system class path, it will be loaded from there rather than the submitted jar file, but now users need not (and should not) put job classfiles on the system classpath. This patch also allows config files to be put in a configuration directory rather than on the classpath, which also eliminates some confusing behavior when there are duplicate instances of config files in different parts of the classpath. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira