Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 58413 invoked from network); 23 Mar 2008 13:55:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 23 Mar 2008 13:55:25 -0000 Received: (qmail 3200 invoked by uid 500); 23 Mar 2008 13:55:23 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 3172 invoked by uid 500); 23 Mar 2008 13:55:23 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 3158 invoked by uid 99); 23 Mar 2008 13:55:23 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 23 Mar 2008 06:55:23 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 23 Mar 2008 13:54:52 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 6D321234C0B4 for ; Sun, 23 Mar 2008 06:53:24 -0700 (PDT) Message-ID: <379367263.1206280404446.JavaMail.jira@brutus> Date: Sun, 23 Mar 2008 06:53:24 -0700 (PDT) From: "Hadoop QA (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Commented: (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 [ https://issues.apache.org/jira/browse/HADOOP-1622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12581384#action_12581384 ] Hadoop QA commented on HADOOP-1622: ----------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12378428/HADOOP-1622_2.patch against trunk revision 619744. @author +1. The patch does not contain any @author tags. tests included +1. The patch appears to include 16 new or modified tests. javadoc +1. The javadoc tool did not generate any warning messages. javac +1. The applied patch does not generate any new javac compiler warnings. release audit +1. The applied patch does not generate any new release audit warnings. findbugs -1. The patch appears to introduce 3 new Findbugs warnings. core tests +1. The patch passed core unit tests. contrib tests +1. The patch passed contrib unit tests. Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2030/testReport/ Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2030/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2030/artifact/trunk/build/test/checkstyle-errors.html Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2030/console This message is automatically generated. > 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 Core > Issue Type: Improvement > Components: mapred > Reporter: Runping Qi > Assignee: Mahadev konar > Fix For: 0.17.0 > > Attachments: hadoop-1622-4-20071008.patch, HADOOP-1622-5.patch, HADOOP-1622-6.patch, HADOOP-1622-7.patch, HADOOP-1622-8.patch, HADOOP-1622-9.patch, HADOOP-1622_1.patch, HADOOP-1622_2.patch, multipleJobJars.patch, multipleJobResources.patch, multipleJobResources2.patch > > > 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.