Return-Path: Delivered-To: apmail-lucene-hadoop-dev-archive@locus.apache.org Received: (qmail 50801 invoked from network); 17 Jul 2007 18:53:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 17 Jul 2007 18:53:33 -0000 Received: (qmail 41275 invoked by uid 500); 17 Jul 2007 18:53:29 -0000 Delivered-To: apmail-lucene-hadoop-dev-archive@lucene.apache.org Received: (qmail 41239 invoked by uid 500); 17 Jul 2007 18:53:29 -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 41200 invoked by uid 99); 17 Jul 2007 18:53:29 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Jul 2007 11:53:28 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Jul 2007 11:53:25 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id B7A9B714204 for ; Tue, 17 Jul 2007 11:53:04 -0700 (PDT) Message-ID: <17905327.1184698384749.JavaMail.jira@brutus> Date: Tue, 17 Jul 2007 11:53:04 -0700 (PDT) From: "Runping Qi (JIRA)" To: hadoop-dev@lucene.apache.org Subject: [jira] Created: (HADOOP-1622) Hadoop should provide a way to allow the user to specify jar file(s) the user job depends on MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hadoop should provide a way to allow the user to specify jar file(s) the user job depends on -------------------------------------------------------------------------------------------- Key: HADOOP-1622 URL: https://issues.apache.org/jira/browse/HADOOP-1622 Project: Hadoop Issue Type: Improvement Reporter: Runping Qi More likely than not, a user's job may depend on multiple jars. Right now, when submitting a job through bin/hadoop, there is no way for the user to specify that. A walk around for that is to re-package all the dependent jars into a new jar or put the dependent jar files in the lib dir of the new jar. This walk around causes unnecessary inconvenience to the user. Furthermore, if the user does not own the main function (like the case when the user uses Aggregate, or datajoin, streaming), the user has to re-package those system jar files too. It is much desired that hadoop provides a clean and simple way for the user to specify a list of dependent jar files at the time of job submission. Someting like: bin/hadoop .... --depending_jars j1.jar:j2.jar -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.