You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Amareshwari Sriramadasu (JIRA)" <ji...@apache.org> on 2009/05/19 09:49:46 UTC

[jira] Commented: (HADOOP-4864) -libjars with multiple jars broken when client and cluster reside on different OSs

    [ https://issues.apache.org/jira/browse/HADOOP-4864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12710654#action_12710654 ] 

Amareshwari Sriramadasu commented on HADOOP-4864:
-------------------------------------------------

The same changes will be required in addFileToClassPath and getFileClassPaths methods also.

> -libjars with multiple jars broken when client and cluster reside on different OSs
> ----------------------------------------------------------------------------------
>
>                 Key: HADOOP-4864
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4864
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: filecache
>    Affects Versions: 0.19.0
>         Environment: When your hadoop job spans OSs.
>            Reporter: Stuart White
>            Priority: Minor
>         Attachments: patch.txt
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> When submitting a hadoop job from Windows (Cygwin) to a Linux hadoop cluster (or vice versa), and when you specify multiple additional jar files via the -libjars flag, hadoop throws a ClassNotFoundException for any classes located in the additional jars specified via the -libjars flag.
> This is caused by the fact that hadoop uses system.getProperty("path.separator") as the delimiter in the list of jar files passed via -libjars.
> My suggested solution is to use a comma as the delimiter, rather than the path.separator.
> I realize comma is, perhaps, a poor choice for a delimiter because it is valid in filenames on both Windows and Linux, but the -libjars flag uses it as the delimiter when listing the additional required jars.  So, I figured if it's already being used as a delimiter, then it's reasonable to use it internally as well.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.