Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Thu, 29 Sep 2011 17:39:45 +0000 (UTC)
From: "Abhijit Suresh Shingate (Assigned) (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <1403682480.8289.1317317985760.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1647909524.8191.1317316065518.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Assigned] (MAPREDUCE-3122) -libjars with streaming does not
 create symlink in the cwd of task
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/MAPREDUCE-3122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Abhijit Suresh Shingate reassigned MAPREDUCE-3122:
--------------------------------------------------

    Assignee: Abhijit Suresh Shingate
    
> -libjars with streaming does not create symlink in the cwd of task
> ------------------------------------------------------------------
>
>                 Key: MAPREDUCE-3122
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3122
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: contrib/streaming
>    Affects Versions: 0.20.205.0
>            Reporter: Ramya Sunil
>            Assignee: Abhijit Suresh Shingate
>
> When libjars option is used with streaming, the symlink to the jar file is not created in the working dir of the task. Any map/reduce tasks which uses this jar fails with NoClassDefFoundError
> For e.g:
> $ hadoop jar hadoop-streaming.jar -libjars /home/ramya/HelloWorld.jar -input input.txt -output Out -mapper "mapper.sh" -reducer NONE -file /home/ramya/mapper.sh
> $ cat /home/ramya/mapper.sh
> #!/bin/sh
> cat &> /dev/null
> java -cp HelloWorld.jar HelloWorld
> $ java -cp /home/ramya/HelloWorld.jar HelloWorld
> Hello World

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira